Skyvern - bug fix to run-workflow action

[michelle0927]

Resolves #16903

Summary by CodeRabbit

• New Features

  • Updated property names in the "Run Workflow" action to use snake_case formatting for improved consistency.

• Chores

  • Incremented version numbers for the "Run Workflow" action and the related package.

[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)			Jun 2, 2025 4:14pm
pipedream-docs	⬜️ Ignored (Inspect)			Jun 2, 2025 4:14pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jun 2, 2025 4:14pm

[coderabbitai]

Walkthrough

The changes update the "Run Workflow" action and its package version. The action now sends the webhook callback URL and proxy location using snake_case property names (webhook_callback_url and proxy_location) in the payload, instead of camelCase. No other logic or functionality was altered.

Changes

File(s)	Change Summary
components/skyvern/actions/run-workflow/run-workflow.mjs	Updated payload property names to snake_case; bumped version to 0.0.2
components/skyvern/package.json	Incremented package version from 0.1.0 to 0.1.1

Assessment against linked issues

Objective	Addressed	Explanation
Ensure webhookCallbackUrl is sent in the request payload to Skyvern (#16903)	✅

Poem

A bunny leaps with joy anew,
For workflows run with names askew—
Snake_case now, the callback flies,
To Skyvern’s gate beneath the skies.
Version numbers hop ahead,
Bugs are fixed, and code is fed!
🐇✨

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/skyvern/actions/run-workflow/run-workflow.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 Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:170:49)

✨ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

components/skyvern/actions/run-workflow/run-workflow.mjs (1)

38-39: Validate payload field naming.

You’ve switched proxyLocation → proxy_location and webhookCallbackUrl → webhook_callback_url. Confirm that the Skyvern API expects these snake_case keys. Consider adding an integration or unit test that mocks triggerWorkflow to catch any mismatches at build time.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ce38964 and 04dc313.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• components/skyvern/actions/run-workflow/run-workflow.mjs (2 hunks)
• components/skyvern/package.json (1 hunks)

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

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

🔇 Additional comments (1)

components/skyvern/actions/run-workflow/run-workflow.mjs (1)

8-8: Verify action version bump.

The action’s version was updated to 0.0.2, which aligns with the package bump. Ensure your release process, CHANGELOG, and any external references (docs or downstream consumers) are updated to use 0.0.2.

[jcortes]

Hi @michelle0927 lgtm! Ready for QA!