Skip to content

[TRIGGER] Use Webhooks for Vercel Sources #16570

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 9, 2025
Merged

Conversation

jcortes
Copy link
Collaborator

@jcortes jcortes commented May 6, 2025

WHY

Resolves #16561

Summary by CodeRabbit

  • New Features

    • Introduced instant event sources for Vercel deployments: "Deployment Canceled", "Deployment Error", "Deployment Succeeded", and "New Deployment" for real-time notifications.
    • Added centralized event name constants for consistent event handling.
    • Implemented a new webhook handler for streamlined integration with Vercel webhooks.
  • Improvements

    • Enhanced team selection options with customizable mapping in the team property.
    • Added new constants for webhook identification and secret management.
  • Chores

    • Updated package version and added a new dependency.
    • Incremented version numbers for several existing actions and sources.

@jcortes jcortes self-assigned this May 6, 2025
Copy link

vercel bot commented May 6, 2025

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) Visit Preview May 9, 2025 2:03pm
pipedream-docs ⬜️ Ignored (Inspect) May 9, 2025 2:03pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) May 9, 2025 2:03pm

Copy link
Contributor

coderabbitai bot commented May 6, 2025

Walkthrough

This update introduces webhook-based event sources for Vercel integration, adding shared modules for event constants and webhook handling, and implementing new instant event sources for deployment lifecycle events. The package version is incremented, new dependencies are added, and minor version bumps are applied to existing actions and sources. The app's team option mapping is also enhanced.

Changes

Files/Groups Change Summary
components/vercel_token_auth/actions/cancel-deployment.mjs
components/vercel_token_auth/actions/create-deployment.mjs
components/vercel_token_auth/actions/list-deployments.mjs
components/vercel_token_auth/sources/new-deployment/new-deployment.mjs
Incremented version numbers from 0.0.4 to 0.0.5 in action/source metadata. No other code or logic changes.
components/vercel_token_auth/package.json Bumped package version from 0.0.5 to 0.1.0 and added "crypto" (v1.0.1) as a dependency.
components/vercel_token_auth/common/constants.mjs Added two exported string constants: WEBHOOK_ID and WEBHOOK_SECRET.
components/vercel_token_auth/sources/common/events.mjs Introduced a new module exporting an object of string constants for all supported Vercel webhook event names.
components/vercel_token_auth/sources/common/webhook.mjs Added a new shared webhook handler module with methods for webhook lifecycle management, signature validation, event processing, and persistent storage of webhook credentials.
components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs
components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs
components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs
components/vercel_token_auth/sources/new-deployment-instant/new-deployment-instant.mjs
Added four new instant event sources for deployment canceled, deployment error, deployment succeeded, and new deployment events. Each source extends the common webhook handler, specifies its event type, and provides metadata generation.
components/vercel_token_auth/vercel_token_auth.app.mjs Updated the options method for the team property to accept an optional mapper function, allowing custom mapping of team objects to option pairs.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Source (e.g. New Deployment Instant)
    participant Webhook Base
    participant Vercel API
    participant Database

    User->>Source: Activate source
    Source->>Webhook Base: activate()
    Webhook Base->>Vercel API: createWebhook(events, endpoint, ...)
    Vercel API-->>Webhook Base: webhookId, webhookSecret
    Webhook Base->>Database: Store webhookId, webhookSecret

    Vercel API-->>Source: Send webhook event (HTTP POST)
    Source->>Webhook Base: run({body, headers, bodyRaw})
    Webhook Base->>Database: Retrieve webhookSecret
    Webhook Base->>Webhook Base: Validate signature
    Webhook Base->>Source: processResource(resource)
    Source->>User: Emit event with metadata

    User->>Source: Deactivate source
    Source->>Webhook Base: deactivate()
    Webhook Base->>Database: Retrieve webhookId
    Webhook Base->>Vercel API: deleteWebhook(webhookId)
Loading

Assessment against linked issues

Objective Addressed Explanation
Update Vercel sources to use webhooks (per Vercel API documentation) [#16561]

Poem

In the warren, code hops anew,
Webhooks leap where polling once grew.
Deployments, errors, and cancels—oh my!
Now trigger in real time as changes fly.
With secrets and IDs tucked in tight,
This bunny’s code is working right!
🐇✨

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/vercel_token_auth/actions/cancel-deployment/cancel-deployment.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/vercel_token_auth/actions/create-deployment/create-deployment.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/vercel_token_auth/actions/list-deployments/list-deployments.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)

  • 9 others

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


📜 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 d10ee4d and dbf1dd4.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (13)
  • components/vercel_token_auth/actions/cancel-deployment/cancel-deployment.mjs (1 hunks)
  • components/vercel_token_auth/actions/create-deployment/create-deployment.mjs (1 hunks)
  • components/vercel_token_auth/actions/list-deployments/list-deployments.mjs (1 hunks)
  • components/vercel_token_auth/common/constants.mjs (1 hunks)
  • components/vercel_token_auth/package.json (2 hunks)
  • components/vercel_token_auth/sources/common/events.mjs (1 hunks)
  • components/vercel_token_auth/sources/common/webhook.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/new-deployment-instant/new-deployment-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/new-deployment/new-deployment.mjs (1 hunks)
  • components/vercel_token_auth/vercel_token_auth.app.mjs (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (10)
  • components/vercel_token_auth/actions/list-deployments/list-deployments.mjs
  • components/vercel_token_auth/sources/new-deployment/new-deployment.mjs
  • components/vercel_token_auth/actions/cancel-deployment/cancel-deployment.mjs
  • components/vercel_token_auth/actions/create-deployment/create-deployment.mjs
  • components/vercel_token_auth/common/constants.mjs
  • components/vercel_token_auth/package.json
  • components/vercel_token_auth/vercel_token_auth.app.mjs
  • components/vercel_token_auth/sources/common/events.mjs
  • components/vercel_token_auth/sources/new-deployment-instant/new-deployment-instant.mjs
  • components/vercel_token_auth/sources/common/webhook.mjs
🧰 Additional context used
🪛 GitHub Check: Lint Code Base
components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: pnpm publish
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
✨ 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
🪧 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 8

🔭 Outside diff range comments (1)
components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs (1)

4-28: 🛠️ Refactor suggestion

Source name should start with "New" per Pipedream guidelines.

The static analysis tool flagged that source names should start with "New" according to Pipedream guidelines (https://pipedream.com/docs/components/guidelines/#source-name).

Update the source name to follow the guideline:

- name: "Deployment Canceled (Instant)",
+ name: "New Deployment Canceled",

The rest of the implementation looks solid, with good separation of concerns, proper extension of the common webhook base, and clear metadata generation.

🧰 Tools
🪛 GitHub Check: Lint Code Base

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

🧹 Nitpick comments (2)
components/vercel_token_auth/sources/common/events.mjs (1)

1-45: Centralized event constants need clarification for naming variations.

Centralizing event constants is good practice for consistency. However, there are duplicate-looking events with different formats:

  • Some use dot notation (e.g., DEPLOYMENT_READY: "deployment.ready")
  • Others use hyphens (e.g., DEPLOYMENT_READY_: "deployment-ready")

This could cause confusion for developers.

Consider adding comments to explain the reason for these variations, such as:

export default {
+ // Standard webhook event types using dot notation
  BUDGET_REACHED: "budget.reached",
  BUDGET_RESET: "budget.reset",
  // ... other dot notation events ...
  
+ // Alternative event format using hyphens (explain why these exist)
  DEPLOYMENT_CHECKS_COMPLETED: "deployment-checks-completed",
  DEPLOYMENT_READY_: "deployment-ready",
  // ... other hyphenated events ...
};
components/vercel_token_auth/sources/common/webhook.mjs (1)

136-147: Nit: spelling & code readability

incommingSignatureincomingSignature (twice). Purely cosmetic but aids comprehension.

-    const incommingSignature = headers["x-vercel-signature"];
+    const incomingSignature = headers["x-vercel-signature"];
...
-    const isValid = this.isSignatureValid(incommingSignature, bodyRaw);
+    const isValid = this.isSignatureValid(incomingSignature, bodyRaw);
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b04188f and 9b05477.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (14)
  • components/vercel_token_auth/actions/cancel-deployment/cancel-deployment.mjs (1 hunks)
  • components/vercel_token_auth/actions/create-deployment/create-deployment.mjs (1 hunks)
  • components/vercel_token_auth/actions/list-deployments/list-deployments.mjs (1 hunks)
  • components/vercel_token_auth/common/constants.mjs (1 hunks)
  • components/vercel_token_auth/package.json (2 hunks)
  • components/vercel_token_auth/sources/common/events.mjs (1 hunks)
  • components/vercel_token_auth/sources/common/webhook.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-ready-instant/deployment-ready-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/new-deployment-instant/new-deployment-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/new-deployment/new-deployment.mjs (1 hunks)
  • components/vercel_token_auth/vercel_token_auth.app.mjs (1 hunks)
🧰 Additional context used
🪛 GitHub Check: Lint Code Base
components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-ready-instant/deployment-ready-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: pnpm publish
  • GitHub Check: Publish TypeScript components
🔇 Additional comments (8)
components/vercel_token_auth/package.json (2)

3-3: Confirm semantic version bump
The version has been updated from 0.0.5 to 0.1.0, which aligns with adding new webhook-based event sources and major feature enhancements. This increment appropriately reflects the introduction of new functionality.


16-17: Verify necessity of npm crypto dependency
Node.js provides a built-in crypto module. Please confirm that you require the npm crypto package (^1.0.1) rather than the core module—if the built-in API suffices, consider removing the extra dependency to reduce bundle size.

components/vercel_token_auth/actions/list-deployments/list-deployments.mjs (1)

7-7: Consistent version bump
Version has been updated from 0.0.4 to 0.0.5 to stay in sync with the package’s new 0.1.0 release. No functional changes detected—this is purely a metadata update.

components/vercel_token_auth/sources/new-deployment/new-deployment.mjs (1)

8-8: Consistent version bump
The source version was bumped from 0.0.4 to 0.0.5, matching the coordinated release across actions and other sources. No other modifications; looks good.

components/vercel_token_auth/actions/cancel-deployment/cancel-deployment.mjs (1)

7-7: Consistent version bump
Updated the action version from 0.0.4 to 0.0.5 in line with the overall package release. No logical changes—only metadata.

components/vercel_token_auth/actions/create-deployment/create-deployment.mjs (1)

8-8: Consistent version bump
Version incremented from 0.0.4 to 0.0.5 to synchronize with related modules. No code logic was altered.

components/vercel_token_auth/common/constants.mjs (1)

12-13: LGTM: Constants added for webhook identification and secret.

The new constants follow the naming conventions of the file and will enable consistent reference to webhook IDs and secrets across the codebase.

components/vercel_token_auth/vercel_token_auth.app.mjs (1)

47-58: Good improvement: Enhanced flexibility with customizable mapper function.

The refactoring of the team options method to accept an optional mapper function increases the component's flexibility while maintaining backward compatibility through the default implementation.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

♻️ Duplicate comments (6)
components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs (2)

7-7: 🛠️ Refactor suggestion

Rename the source to comply with Pipedream naming guidelines

Lint warns that source names should start with "New". Renaming avoids a pipeline failure and keeps the catalogue consistent.

-  name: "Deployment Error (Instant)",
+  name: "New Deployment Error (Instant)",
🧰 Tools
🪛 GitHub Check: Lint Code Base

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name


21-24: ⚠️ Potential issue

createdAt may be undefined – fall back to created

Vercel's deployment payload exposes a created (Unix ms) field, not createdAt. Referencing a non-existent property will set ts to undefined, breaking deduping and event ordering.

-        ts: resource.createdAt,
+        ts: resource.createdAt ?? resource.created,
components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs (2)

7-7: 🛠️ Refactor suggestion

Prefix source name with "New" to satisfy lint rules

-  name: "Deployment Succeeded (Instant)",
+  name: "New Deployment Succeeded (Instant)",
🧰 Tools
🪛 GitHub Check: Lint Code Base

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name


21-24: ⚠️ Potential issue

Guard against missing createdAt in Vercel payload

Same rationale as previous files - Vercel uses created rather than createdAt for timestamps.

-        ts: resource.createdAt,
+        ts: resource.createdAt ?? resource.created,
components/vercel_token_auth/sources/deployment-ready-instant/deployment-ready-instant.mjs (2)

7-7: 🛠️ Refactor suggestion

Fix lint violation: source names must begin with "New"

-  name: "Deployment Ready (Instant)",
+  name: "New Deployment Ready (Instant)",
🧰 Tools
🪛 GitHub Check: Lint Code Base

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name


21-24: ⚠️ Potential issue

Fallback when createdAt is absent

-        ts: resource.createdAt,
+        ts: resource.createdAt ?? resource.created,
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9b05477 and fda2abd.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (14)
  • components/vercel_token_auth/actions/cancel-deployment/cancel-deployment.mjs (1 hunks)
  • components/vercel_token_auth/actions/create-deployment/create-deployment.mjs (1 hunks)
  • components/vercel_token_auth/actions/list-deployments/list-deployments.mjs (1 hunks)
  • components/vercel_token_auth/common/constants.mjs (1 hunks)
  • components/vercel_token_auth/package.json (2 hunks)
  • components/vercel_token_auth/sources/common/events.mjs (1 hunks)
  • components/vercel_token_auth/sources/common/webhook.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-ready-instant/deployment-ready-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/new-deployment-instant/new-deployment-instant.mjs (1 hunks)
  • components/vercel_token_auth/sources/new-deployment/new-deployment.mjs (1 hunks)
  • components/vercel_token_auth/vercel_token_auth.app.mjs (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • components/vercel_token_auth/package.json
🚧 Files skipped from review as they are similar to previous changes (9)
  • components/vercel_token_auth/sources/new-deployment/new-deployment.mjs
  • components/vercel_token_auth/actions/cancel-deployment/cancel-deployment.mjs
  • components/vercel_token_auth/actions/create-deployment/create-deployment.mjs
  • components/vercel_token_auth/actions/list-deployments/list-deployments.mjs
  • components/vercel_token_auth/common/constants.mjs
  • components/vercel_token_auth/sources/common/events.mjs
  • components/vercel_token_auth/sources/common/webhook.mjs
  • components/vercel_token_auth/sources/new-deployment-instant/new-deployment-instant.mjs
  • components/vercel_token_auth/vercel_token_auth.app.mjs
🧰 Additional context used
🪛 GitHub Check: Lint Code Base
components/vercel_token_auth/sources/deployment-canceled-instant/deployment-canceled-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-error-instant/deployment-error-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-ready-instant/deployment-ready-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

components/vercel_token_auth/sources/deployment-succeeded-instant/deployment-succeeded-instant.mjs

[warning] 7-7:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: pnpm publish
  • GitHub Check: Publish TypeScript components

luancazarine
luancazarine previously approved these changes May 7, 2025
Copy link
Collaborator

@luancazarine luancazarine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jcortes, LGTM! Ready for QA!

@jcortes jcortes force-pushed the vercel-use-webhooks branch from d10ee4d to dbf1dd4 Compare May 9, 2025 14:03
@jcortes
Copy link
Collaborator Author

jcortes commented May 9, 2025

/approve

@jcortes jcortes merged commit 93f2094 into master May 9, 2025
11 checks passed
@jcortes jcortes deleted the vercel-use-webhooks branch May 9, 2025 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[TRIGGER] Use Webhooks for Vercel Sources
2 participants