[Pipedrive] fix webhooks v1

[andrewjschuang]

WHY

Summary by CodeRabbit

• Chores
  • Updated version identifiers across multiple components to the newest release.
  • Specified the supported webhook integration version for improved consistency.
  • Maintained existing functionalities without impacting end-user behavior.

[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)			Apr 10, 2025 0:54am
pipedream-docs	⬜️ Ignored (Inspect)			Apr 10, 2025 0:54am
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Apr 10, 2025 0:54am

[coderabbitai]

Walkthrough

This pull request updates version numbers across several Pipedrive component files. The package.json version is bumped from "0.3.11" to "0.3.12". Additionally, a new property (version: "1.0") is added in the activate hook of the base module to clarify webhook versioning due to the upcoming default change. Other source files—for new deal, new person, updated deal, and updated person instants—have their exported version updated from "0.0.1" to "0.0.2".

Changes

File(s)	Change Summary
components/pipedrive/package.json	Updated version from "0.3.11" to "0.3.12".
components/pipedrive/sources/common/base.mjs	Added version: "1.0" in the activate hook with a comment explaining the webhook version change.
components/pipedrive/sources/new-deal-instant/new-deal-instant.mjs components/pipedrive/sources/new-person-instant/new-person-instant.mjs components/pipedrive/sources/updated-deal-instant/updated-deal-instant.mjs components/pipedrive/sources/updated-person-instant/updated-person-instant.mjs	Updated exported version from "0.0.1" to "0.0.2".

Sequence Diagram(s)

sequenceDiagram
    participant Base as Base Module (activate hook)
    participant Pipedrive as this.pipedrive
    Base->>Pipedrive: addWebhook({ version: "1.0", ... })
    Pipedrive-->>Base: Acknowledgement

Loading

Possibly related PRs

• OpenPhone Usability Audit #16165: Also updates version numbers in various files, including changes in the create-contact.mjs file, indicating a consistent focus on version management.

Poem

I'm a rabbit hopping through the code,
Updating versions on every node.
"1.0" whispers in the webhook call,
Instants bloom as versions stand tall.
In Pipedrive meadows, our changes proudly crawl! 🐰✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/pipedrive/sources/common/base.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

components/pipedrive/sources/new-person-instant/new-person-instant.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

components/pipedrive/sources/new-deal-instant/new-deal-instant.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

• 2 others

---

📜 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 4329ac8 and b52c6a1.

📒 Files selected for processing (6)

• components/pipedrive/package.json (1 hunks)
• components/pipedrive/sources/common/base.mjs (1 hunks)
• components/pipedrive/sources/new-deal-instant/new-deal-instant.mjs (1 hunks)
• components/pipedrive/sources/new-person-instant/new-person-instant.mjs (1 hunks)
• components/pipedrive/sources/updated-deal-instant/updated-deal-instant.mjs (1 hunks)
• components/pipedrive/sources/updated-person-instant/updated-person-instant.mjs (1 hunks)

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

• GitHub Check: pnpm publish
• GitHub Check: Verify TypeScript components
• GitHub Check: Publish TypeScript components

🔇 Additional comments (6)

components/pipedrive/package.json (1)

3-3: Bump package version to 0.3.12
The version update in the package.json file now reflects the broader changes across the Pipedrive components. Please ensure that this change remains consistent with release notes and any dependent modules.

components/pipedrive/sources/new-deal-instant/new-deal-instant.mjs (1)

9-9: Update new deal instant module version to 0.0.2
The version property has been correctly updated from "0.0.1" to "0.0.2". This aligns with the versioning strategy across similar source modules.

components/pipedrive/sources/updated-deal-instant/updated-deal-instant.mjs (1)

9-9: Bump updated deal instant module version to 0.0.2
The version update to "0.0.2" is consistent with the other modules and helps maintain uniformity. No issues detected with this change.

components/pipedrive/sources/new-person-instant/new-person-instant.mjs (1)

9-9: Update new person instant module version to 0.0.2
The module’s version property has been bumped from "0.0.1" to "0.0.2", which is consistent with the overall versioning updates for the Pipedrive components.

components/pipedrive/sources/updated-person-instant/updated-person-instant.mjs (1)

9-9: Set updated person instant module version to 0.0.2
This change aligns the version number with the rest of the sources. It’s a straightforward update that ensures consistency across all similar modules.

components/pipedrive/sources/common/base.mjs (1)

23-25: Clarify and Validate Webhook Versioning

The addition of version: "1.0", along with the explanatory comment is a clear and useful update that ensures consumers know the webhook is explicitly set to v1, especially in light of the upcoming default change to v2. Please verify that this version setting is fully compatible with both upstream expectations and any downstream integrations.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.