Bigdatacorp bump versions

[michelle0927]

Bump versions to republish #15028

Summary by CodeRabbit

• Chores
  • Updated version numbers for BigDataCorp components and package
  • Incremented package version from 0.1.0 to 0.1.1
  • Updated individual component versions from 0.0.1 to 0.0.2

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Jan 9, 2025 4:40pm
pipedream-docs	⬜️ Ignored (Inspect)			Jan 9, 2025 4:40pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jan 9, 2025 4:40pm

[coderabbitai]

Walkthrough

This pull request involves version updates across multiple files within the BigDataCorp component. Specifically, the version numbers have been incremented in three action files (get-address-data.mjs, get-company-data.mjs, and get-person-data.mjs) from "0.0.1" to "0.0.2", and the package.json file's version has been updated from "0.1.0" to "0.1.1". These changes appear to be routine version increments with no functional modifications to the code.

Changes

File	Change Summary
components/bigdatacorp/actions/.../get-address-data.mjs	Version updated from "0.0.1" to "0.0.2"
components/bigdatacorp/actions/.../get-company-data.mjs	Version updated from "0.0.1" to "0.0.2"
components/bigdatacorp/actions/.../get-person-data.mjs	Version updated from "0.0.1" to "0.0.2"
components/bigdatacorp/package.json	Package version updated from "0.1.0" to "0.1.1"

Possibly related PRs

• [Components] xata #13198 #13853: Version update for @pipedream/xata package
• Gmail - Update verify-client-id #13959: Version increment for @pipedream/gmail package
• Hubspot version update #14816: Version change for @pipedream/hubspot package
• Hubspot - Update Deal #14891: Version update for @pipedream/hubspot package
• Notion Update Page Dynamic Fields #15002: Version increment for @pipedream/notion package
• Update zoho_subscriptions to use Zoho Billing API endpoints #15036: Version update for @pipedream/zoho_subscriptions package
• Bumping version of Firebase Admin SDK to pick up latest version. Fixes #15033 #15039: Version change for @pipedream/firebase_admin_sdk package
• update in url #15078: Version increment for @pipedream/remote_retrieval package
• Lusha - fix prop #15104: Version update for @pipedream/lusha package
• Hubspot new task version fix #15216: Version change for @pipedream/hubspot package
• Gmail Invalid thread_id #15229: Version increment for @pipedream/gmail package

Suggested labels

user submitted

Suggested reviewers

• jcortes

Poem

🐰 A version bump, oh so slight,
Numbers dancing in digital light,
From zero-point-one to zero-point-two,
A rabbit's code update rings true!
Small steps forward, version's delight 🔢

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 665c04f and e99971b.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• components/bigdatacorp/actions/get-address-data/get-address-data.mjs (1 hunks)
• components/bigdatacorp/actions/get-company-data/get-company-data.mjs (1 hunks)
• components/bigdatacorp/actions/get-person-data/get-person-data.mjs (1 hunks)
• components/bigdatacorp/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (4)

• components/bigdatacorp/actions/get-address-data/get-address-data.mjs
• components/bigdatacorp/actions/get-company-data/get-company-data.mjs
• components/bigdatacorp/actions/get-person-data/get-person-data.mjs
• components/bigdatacorp/package.json

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Verify TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Publish TypeScript components
• GitHub Check: Lint Code Base

Finishing Touches

• 📝 Generate Docstrings

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.