Configure file stash sync: Ragie-Zoho WorkDrive #17375

js07 · 2025-06-30T23:10:20Z

Adds dir props to relevant components for apps starting with 'R' to 'Z'.

WHY

The 'dir' prop indicates that a stash ID should be passed when running these actions via the Connect API. This allows files written to the ephemeral /tmp directory in one action to be read by another, separately executed action since both can sync /tmp with the same File Stash directory.

Summary by CodeRabbit

New Features
- Added a new optional syncDir property to numerous actions, allowing users to specify a directory for file synchronization with configurable read or write access.
- Updated several actions to use the syncDir property for improved file handling and synchronization.
- Some actions now return file path information after file operations.
Chores
- Incremented version numbers across multiple components and actions for consistency and tracking.

The 'dir' prop indicates that a stash ID should be passed when running these actions via the Connect API. This allows files written to the ephemeral /tmp directory in one action to be read by another, separately executed action since both can sync /tmp with the same File Stash directory.

vercel · 2025-06-30T23:10:26Z

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

3 Skipped Deployments

Name	Status	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Jun 30, 2025 11:10pm
pipedream-docs	⬜️ Ignored (Inspect)	Jun 30, 2025 11:10pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)	Jun 30, 2025 11:10pm

coderabbitai · 2025-06-30T23:10:27Z

Walkthrough

This update introduces a new optional syncDir property to the props of numerous action modules across many components. The syncDir property enables directory synchronization with configurable access modes (read or write) and is marked as optional in most cases. Additionally, package and action version numbers have been incremented to reflect these changes. A few actions have minor logic adjustments to support dynamic directory paths, but most logic remains unchanged.

Changes

File(s)	Change Summary
`components//actions//` (multiple action files)	Added optional `syncDir` prop of type `dir` (with `read` or `write` access and `sync: true`). Incremented action version numbers. Some actions updated return values or file path logic to use the new directory prop.
`components/*/package.json` (all affected components)	Incremented package version numbers. No other metadata or dependency changes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Action
    participant SyncDir

    User->>Action: Invoke action with props (including optional syncDir)
    alt syncDir is provided
        Action->>SyncDir: Access or write files in syncDir (read/write)
        SyncDir-->>Action: Directory contents or file path
    else syncDir not provided
        Action->>Action: Use default directory (e.g., /tmp)
    end
    Action-->>User: Return result (may include file path if relevant)

Poem

🐇
A hop, a skip, a syncDir here,
New props appear, the path is clear!
Versions rise with every leap,
Directories now yours to keep.
From read to write, the bunnies cheer—
CodeRabbit brings new sync this year!
🌱

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/ragie/actions/create-document/create-document.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:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/ragie/actions/update-document-file/update-document-file.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:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/raindrop/actions/parse-bookmark-file/parse-bookmark-file.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:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

61 others

✨ 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.
- 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: 5

🔭 Outside diff range comments (8)

components/transifex/package.json (1)
15-18: Remove the spurious fs dependency

fs is a core Node.js module; adding it to package.json pulls in the placeholder [email protected] package, creating needless bloat and a potential supply-chain risk. Internal guidelines explicitly forbid bundling built-ins.
   "dependencies": {
     "@pipedream/platform": "^3.1.0",
-    "fs": "^0.0.1-security"
+    /* built-in Node module ‑- external dependency not required */
   }
components/spotlightr/package.json (1)
18-18: Remove built-in Node.js module from dependencies.

The fs module is a built-in Node.js module and should not be added to package.json dependencies, as it's provided natively by the Node.js runtime.
-    "fs": "^0.0.1-security"
components/signnow/package.json (1)
17-17: Remove unnecessary built-in Node.js module dependency.

The crypto dependency should be removed as it's a built-in Node.js module that doesn't need to be explicitly declared in package.json.

Apply this diff:
-    "crypto": "^1.0.1",
components/trust/package.json (1)
18-18: Remove the fs dependency - security risk.

The fs module is a built-in Node.js module and should not be listed in package.json dependencies. The version "^0.0.1-security" appears to be a potentially malicious package that could be impersonating the native fs module.

Apply this diff to remove the dependency:
   "dependencies": {
     "@pipedream/platform": "^3.1.0",
-    "form-data": "^4.0.0",
-    "fs": "^0.0.1-security"
+    "form-data": "^4.0.0"
   }
components/testmonitor/package.json (1)
13-16: fs must NOT be declared as a dependency

fs is a built-in Node.js module and should never be listed in package.json dependencies. Publishing with this entry will install the bogus fs placeholder package from npm, potentially breaking your component at runtime.
   "dependencies": {
     "@pipedream/platform": "^3.1.0",
-    "fs": "^0.0.1-security",
     "moment": "^2.29.4"
   },
components/tinypng/package.json (1)
15-19: Remove built-in Node.js modules from dependencies
We’ve verified that the Tinypng component only uses Node’s core “stream” and “util” modules (via ESM imports), and there are no require("stream") or require("util") calls pulling in the npm polyfills. Removing these entries will let the runtime resolve to the built-in modules, avoiding unnecessary polyfills.

• File to update:

components/tinypng/package.json
   "dependencies": {
     "@pipedream/platform": "^3.1.0",
-    "stream": "^0.0.2",
-    "util": "^0.12.5"
   }
components/sendgrid/package.json (1)
17-17: Remove the built-in fs module from dependencies.

The fs module is a built-in Node.js module and should not be listed in package.json dependencies, as it's provided natively by the Node.js runtime.
-    "fs": "^0.0.1-security",
components/twilio/package.json (1)
3-18: Remove unnecessary dependency on built-in module stream

Per prior guidance, built-in Node modules should not be listed in dependencies. Keeping "stream": "^0.0.3" adds bloat and may pull an outdated polyfill.

Proposed fix:
@@
-    "phone": "^3.1.49",
-    "stream": "^0.0.3",
-    "twilio": "^3.54.2"
+    "phone": "^3.1.49",
+    "twilio": "^3.54.2"

🧹 Nitpick comments (11)

components/scoredetect/actions/create-timestamp-file/create-timestamp-file.mjs (1)
18-23: Add a brief description to syncDir for better UX
The new prop will render in the UI with no hint of why the user might supply it. A one-liner such as "Directory synced between actions (optional)" makes intent clear and keeps component docs self-contained.
     syncDir: {
       type: "dir",
       accessMode: "read",
       sync: true,
       optional: true,
+      label: "Sync Directory",
+      description: "Directory to read shared files from when this action is executed via the Connect API",
     },
components/stannp/actions/create-campaign/create-campaign.mjs (1)
80-85: Add UI metadata to syncDir prop

The new syncDir prop has no label or description, so the PD UI will display the raw key name, which is less user-friendly than the other props in this action. Consider adding them for consistency.
-    syncDir: {
-      type: "dir",
-      accessMode: "read",
-      sync: true,
-      optional: true,
-    },
+    syncDir: {
+      type: "dir",
+      label: "File Stash Directory",
+      description: "Directory to read files written by prior actions in the same workflow run.",
+      accessMode: "read",
+      sync: true,
+      optional: true,
+    },
components/salesforce_rest_api/package.json (1)

3-3: Patch bump acknowledged — remember the release artefacts

The version field moves from 1.6.0 to 1.6.1, which is appropriate for a patch-level change.
Please ensure the changelog / release notes are updated so the reason for this bump is traceable.
components/salesforce_rest_api/actions/create-attachment/create-attachment.mjs (1)
37-45: Consider streaming large files to avoid buffering everything in memory

getFileStream() is fully streamed, but the current implementation buffers the entire file (Buffer.concat(chunks)) before Base64-encoding it.
For multi-MB attachments this can be both memory-intensive and slow.
-const chunks = [];
-for await (const chunk of stream) {
-  chunks.push(chunk);
-}
-body = Buffer.concat(chunks).toString("base64");
+const { pipeline } = await import("node:stream/promises");
+import { Buffer } from "node:buffer";
+import { Transform } from "node:stream";
+
+const base64Encoder = new Transform({
+  transform(chunk, _enc, cb) {
+    cb(null, chunk.toString("base64"));
+  },
+});
+const chunks = [];
+await pipeline(stream, base64Encoder, async function* (source) {
+  for await (const chunk of source) yield chunks.push(chunk);
+});
+body = Buffer.concat(chunks).toString();
This keeps the memory footprint bounded.
components/reform/actions/extract-data-from-document/extract-data-from-document.mjs (1)
26-31: Consider adding description for consistency.

The syncDir property configuration is correct for the intended file stash synchronization functionality. However, consider adding a description for consistency with other properties in the file.
 syncDir: {
+  description: "Directory to sync for file stash operations",
   type: "dir",
   accessMode: "read",
   sync: true,
   optional: true,
 },
components/testmonitor/actions/create-test-result/create-test-result.mjs (1)
72-77: Provide UI metadata for the new syncDir prop

The new syncDir prop lacks a label and description, so users will see a generic field with no guidance in the Pipedream UI. Add them for clarity and consistency with other props.
     syncDir: {
       type: "dir",
       accessMode: "read",
       sync: true,
       optional: true,
+      label: "File Stash Directory",
+      description: "Select the directory to read files from when using File Stash sync.",
     },
components/vapi/package.json (1)

3-3: Confirm changelog + action version parity for 0.1.2 bump

Patch bump is fine for backward-compatible syncDir addition, but remember to:
• add an entry in the component’s CHANGELOG (if maintained), and
• verify every modified action in this package was bumped to ≥ 0.0.3 for consistency.

components/sharepoint/package.json (1)

3-3: 0.3.2 version bump—double-check internal action versions

Make sure all SharePoint actions touched by the syncDir change were bumped (e.g. download-file → 0.0.3) and that release notes reflect the new capability.

components/supabase/package.json (1)

3-3: Verify semver alignment after moving to 0.3.3

Since a new optional prop was added, confirm:

Any affected actions are now ≥ 0.0.4, and

Docs/CHANGELOG mention the new syncDir support.

components/raindrop/package.json (1)

3-3: Patch bump to 0.4.1—update release notes

The package version advances, but remember to publish a concise changelog entry summarizing the syncDir enhancement for bookmark parsing.

components/wordpress_org/package.json (1)

3-3: Ensure docs match 0.4.2 patch release

Please validate that:
• upload-media action is now 0.0.3, and
• README / CHANGELOG mention the new directory-sync prop.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between df8a3b7 and f08d55a.

📒 Files selected for processing (107)

components/ragie/actions/create-document/create-document.mjs (2 hunks)
components/ragie/actions/update-document-file/update-document-file.mjs (2 hunks)
components/ragie/package.json (1 hunks)
components/raindrop/actions/parse-bookmark-file/parse-bookmark-file.mjs (2 hunks)
components/raindrop/package.json (1 hunks)
components/ramp/actions/upload-receipt/upload-receipt.mjs (2 hunks)
components/ramp/package.json (1 hunks)
components/ramp_sandbox/actions/upload-receipt/upload-receipt.mjs (2 hunks)
components/ramp_sandbox/package.json (1 hunks)
components/rapid_url_indexer/actions/download-project-report/download-project-report.mjs (2 hunks)
components/rapid_url_indexer/package.json (1 hunks)
components/reform/actions/extract-data-from-document/extract-data-from-document.mjs (2 hunks)
components/reform/package.json (1 hunks)
components/rendi/actions/run-ffmpeg-command/run-ffmpeg-command.mjs (3 hunks)
components/rendi/package.json (1 hunks)
components/ringcentral/actions/download-recording/download-recording.mjs (2 hunks)
components/ringcentral/package.json (1 hunks)
components/roboflow/actions/classify-image/classify-image.mjs (2 hunks)
components/roboflow/actions/detect-object-from-image/detect-object-from-image.mjs (2 hunks)
components/roboflow/actions/upload-image/upload-image.mjs (2 hunks)
components/roboflow/package.json (1 hunks)
components/salesforce_rest_api/actions/create-attachment/create-attachment.mjs (1 hunks)
components/salesforce_rest_api/package.json (1 hunks)
components/scoredetect/actions/create-timestamp-file/create-timestamp-file.mjs (2 hunks)
components/scoredetect/package.json (1 hunks)
components/scrapfly/actions/ai-data-extraction/ai-data-extraction.mjs (2 hunks)
components/scrapfly/package.json (1 hunks)
components/sendgrid/actions/send-email-multiple-recipients/send-email-multiple-recipients.mjs (2 hunks)
components/sendgrid/actions/send-email-single-recipient/send-email-single-recipient.mjs (2 hunks)
components/sendgrid/package.json (1 hunks)
components/sftp/actions/upload-file/upload-file.mjs (2 hunks)
components/sftp/package.json (1 hunks)
components/sharepoint/actions/download-file/download-file.mjs (2 hunks)
components/sharepoint/package.json (1 hunks)
components/shopify/actions/bulk-import/bulk-import.mjs (2 hunks)
components/shopify/package.json (1 hunks)
components/shortpixel/actions/optimize-image/optimize-image.mjs (2 hunks)
components/shortpixel/package.json (1 hunks)
components/signaturit/actions/create-certified-email/create-certified-email.mjs (2 hunks)
components/signaturit/actions/create-signature-request-from-template/create-signature-request-from-template.mjs (2 hunks)
components/signaturit/package.json (1 hunks)
components/signerx/actions/upload-package/upload-package.mjs (2 hunks)
components/signerx/package.json (1 hunks)
components/signnow/actions/upload-document-with-tags/upload-document-with-tags.mjs (2 hunks)
components/signnow/package.json (1 hunks)
components/slack/actions/upload-file/upload-file.mjs (2 hunks)
components/slack/package.json (1 hunks)
components/smugmug/actions/upload-image/upload-image.mjs (2 hunks)
components/smugmug/package.json (1 hunks)
components/sonix/actions/upload-media/upload-media.mjs (2 hunks)
components/sonix/package.json (1 hunks)
components/speechace/actions/score-scripted-recording/score-scripted-recording.mjs (2 hunks)
components/speechace/actions/transcribe-and-score-recording/transcribe-and-score-recording.mjs (2 hunks)
components/speechace/package.json (1 hunks)
components/spotlightr/actions/create-video/create-video.mjs (2 hunks)
components/spotlightr/package.json (1 hunks)
components/stannp/actions/create-campaign/create-campaign.mjs (2 hunks)
components/stannp/package.json (1 hunks)
components/supabase/actions/batch-insert-rows/batch-insert-rows.mjs (2 hunks)
components/supabase/package.json (1 hunks)
components/syncmate_by_assitro/actions/send-bulk-messages/send-bulk-messages.mjs (2 hunks)
components/syncmate_by_assitro/actions/send-message/send-message.mjs (2 hunks)
components/syncmate_by_assitro/package.json (1 hunks)
components/testmonitor/actions/create-test-result/create-test-result.mjs (2 hunks)
components/testmonitor/package.json (1 hunks)
components/the_bookie/actions/create-sales-invoice/create-sales-invoice.mjs (2 hunks)
components/the_bookie/package.json (1 hunks)
components/tinypng/actions/compress-image/compress-image.mjs (2 hunks)
components/tinypng/actions/convert-image/convert-image.mjs (2 hunks)
components/tinypng/actions/resize-image/resize-image.mjs (2 hunks)
components/tinypng/package.json (1 hunks)
components/todoist/actions/export-tasks/export-tasks.mjs (2 hunks)
components/todoist/actions/import-tasks/import-tasks.mjs (2 hunks)
components/todoist/package.json (1 hunks)
components/transifex/actions/download-file/download-file.mjs (2 hunks)
components/transifex/actions/upload-file/upload-file.mjs (2 hunks)
components/transifex/package.json (1 hunks)
components/trello/actions/add-attachment-to-card/add-attachment-to-card.mjs (2 hunks)
components/trello/actions/create-card/create-card.mjs (2 hunks)
components/trello/package.json (1 hunks)
components/trust/actions/upload-video/upload-video.mjs (2 hunks)
components/trust/package.json (1 hunks)
components/twilio/actions/download-recording-media/download-recording-media.mjs (3 hunks)
components/twilio/package.json (1 hunks)
components/vapi/actions/upload-file/upload-file.mjs (2 hunks)
components/vapi/package.json (1 hunks)
components/what_are_those/actions/find-sneakers-by-sku/find-sneakers-by-sku.mjs (2 hunks)
components/what_are_those/actions/grade-sneakers-condition/grade-sneakers-condition.mjs (2 hunks)
components/what_are_those/actions/identify-sneakers-from-photo/identify-sneakers-from-photo.mjs (2 hunks)
components/what_are_those/package.json (1 hunks)
components/whatsapp_business/actions/send-voice-message/send-voice-message.mjs (2 hunks)
components/whatsapp_business/package.json (1 hunks)
components/wordpress_org/actions/upload-media/upload-media.mjs (2 hunks)
components/wordpress_org/package.json (1 hunks)
components/xero_accounting_api/actions/download-invoice/download-invoice.mjs (3 hunks)
components/xero_accounting_api/actions/upload-file/upload-file.mjs (2 hunks)
components/xero_accounting_api/package.json (1 hunks)
components/youtube_data_api/actions/upload-channel-banner/upload-channel-banner.mjs (2 hunks)
components/youtube_data_api/actions/upload-thumbnail/upload-thumbnail.mjs (2 hunks)
components/youtube_data_api/actions/upload-video/upload-video.mjs (2 hunks)
components/youtube_data_api/package.json (1 hunks)
components/youtube_data_api_custom_app/actions/upload-channel-banner/upload-channel-banner.mjs (2 hunks)
components/youtube_data_api_custom_app/actions/upload-thumbnail/upload-thumbnail.mjs (2 hunks)
components/youtube_data_api_custom_app/actions/upload-video/upload-video.mjs (2 hunks)
components/youtube_data_api_custom_app/package.json (1 hunks)
components/zerobounce/actions/file-validation/file-validation.mjs (2 hunks)
components/zerobounce/actions/get-validation-results-file/get-validation-results-file.mjs (2 hunks)

⛔ Files not processed due to max files limit (11)

components/zerobounce/package.json
components/zip_archive_api/actions/compress-files/compress-files.mjs
components/zip_archive_api/package.json
components/zoho_bugtracker/actions/create-bug/create-bug.mjs
components/zoho_bugtracker/actions/update-bug/update-bug.mjs
components/zoho_bugtracker/package.json
components/zoho_desk/actions/add-ticket-attachment/add-ticket-attachment.mjs
components/zoho_desk/package.json
components/zoho_workdrive/actions/download-file/download-file.mjs
components/zoho_workdrive/actions/upload-file/upload-file.mjs
components/zoho_workdrive/package.json

🧰 Additional context used

🧠 Learnings (58)

components/signnow/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/syncmate_by_assitro/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/shortpixel/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/testmonitor/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/supabase/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/speechace/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/rapid_url_indexer/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/sendgrid/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/raindrop/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/xero_accounting_api/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/what_are_those/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/trello/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/salesforce_rest_api/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/ragie/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/the_bookie/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/todoist/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/smugmug/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/vapi/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/sonix/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/wordpress_org/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/transifex/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/whatsapp_business/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/signerx/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/youtube_data_api/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/slack/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/ramp_sandbox/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/tinypng/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/twilio/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/signaturit/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/salesforce_rest_api/actions/create-attachment/create-attachment.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/stannp/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/shopify/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/sftp/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/ringcentral/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/youtube_data_api_custom_app/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/scrapfly/package.json (2)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#13961
File: components/fakturoid/actions/create-invoice/create-invoice.mjs:95-99
Timestamp: 2024-10-15T15:07:38.361Z
Learning: An "object array" type is not yet supported for Pipedream props.

components/rendi/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/trust/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/ramp/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/stannp/actions/create-campaign/create-campaign.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/spotlightr/package.json (2)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#15376
File: components/monday/sources/column-value-updated/column-value-updated.mjs:17-24
Timestamp: 2025-01-23T03:55:51.998Z
Learning: Alert props in Pipedream components are a special case that do not require a label property, and use the 'content' property as a replacement for description.

components/roboflow/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/sharepoint/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/reform/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/ramp_sandbox/actions/upload-receipt/upload-receipt.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/scoredetect/package.json (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.

components/testmonitor/actions/create-test-result/create-test-result.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/syncmate_by_assitro/actions/send-message/send-message.mjs (3)

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-10-08T15:33:38.240Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-07-04T18:11:59.822Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/trello/actions/create-card/create-card.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/ragie/actions/create-document/create-document.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/speechace/actions/transcribe-and-score-recording/transcribe-and-score-recording.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/todoist/actions/export-tasks/export-tasks.mjs (2)

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-10-08T15:33:38.240Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-07-04T18:11:59.822Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.

components/spotlightr/actions/create-video/create-video.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/syncmate_by_assitro/actions/send-bulk-messages/send-bulk-messages.mjs (3)

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-10-08T15:33:38.240Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-07-04T18:11:59.822Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/the_bookie/actions/create-sales-invoice/create-sales-invoice.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/whatsapp_business/actions/send-voice-message/send-voice-message.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/signaturit/actions/create-certified-email/create-certified-email.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

components/speechace/actions/score-scripted-recording/score-scripted-recording.mjs (1)

Learnt from: jcortes
PR: PipedreamHQ/pipedream#14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In `components/gainsight_px/actions/create-account/create-account.mjs`, the action name should be "Create Account" instead of "Create Memory".

🔇 Additional comments (153)

components/rendi/package.json (1)

3-3: Patch version bump is appropriate and consistent

Adding an optional, non-breaking syncDir prop warrants a patch-level increment, so 0.1.0 → 0.1.1 complies with semver. No further concerns.

components/rapid_url_indexer/package.json (1)

3-3: Double-check that a patch bump is the intended SemVer signal

Introducing the new syncDir prop is a (non-breaking) feature addition rather than a bug-fix. Under SemVer, that’s typically a MINOR bump (0.2.0) even in the 0.x range (where MINOR still communicates “new functionality”).
If the package consumers rely on SemVer semantics, you may want to raise the minor version instead of just patching.

components/scoredetect/package.json (1)

3-3: Version bump looks correct
Package metadata stays intact and there are no extraneous dependency changes.

components/scoredetect/actions/create-timestamp-file/create-timestamp-file.mjs (1)

8-8: Action version updated appropriately
The patch-level increment (0.1.0 → 0.1.1) aligns with the non-breaking addition of a prop.

components/zerobounce/actions/file-validation/file-validation.mjs (2)

9-9: LGTM! Version increment follows standard practice.

The version bump from "0.1.0" to "0.1.1" correctly reflects the addition of the new syncDir property.

65-70: LGTM! syncDir property implementation aligns with PR objectives.

The syncDir property is well-configured for this file validation action:

type: "dir" enables directory synchronization

accessMode: "read" is appropriate since this action likely reads files from the stash

sync: true enables the file stash synchronization feature

optional: true maintains backward compatibility

This implementation correctly supports the Connect API file stash functionality described in the PR objectives.

components/stannp/package.json (1)

3-3: Version bump looks good

Semver increment from 0.2.0 → 0.2.1 is appropriate for an additive, non-breaking change.
Remember to include an entry in the component’s CHANGELOG, if you keep one.

components/stannp/actions/create-campaign/create-campaign.mjs (1)

12-12: Action version updated correctly

Patch-level bump to 0.1.1 accurately signals the purely additive prop change. No issues here.

components/tinypng/actions/resize-image/resize-image.mjs (3)

11-11: LGTM: Version increment is appropriate.

The version bump from "0.0.1" to "0.0.2" correctly reflects the addition of new functionality.

28-32: LGTM: syncDir prop is correctly configured.

The syncDir property is properly defined with:

type: "dir" for directory handling

accessMode: "write" which aligns with this action's behavior of creating resized image files

sync: true to enable file stash synchronization

This configuration supports the PR objective of enabling file sharing between separately executed actions.

73-81: Note: syncDir prop not yet utilized in execution logic.

The action currently writes to a hardcoded /tmp path but doesn't use the syncDir prop yet. This appears to be intentional for a staged rollout where the prop is added first and usage implementation follows.

components/shopify/package.json (1)

3-3: LGTM! Standard version increment.

The package version bump from "0.7.0" to "0.7.1" is appropriate for the addition of new functionality (syncDir property) to the bulk-import action.

components/shopify/actions/bulk-import/bulk-import.mjs (2)

10-10: LGTM! Appropriate version increment.

The action version bump from "0.0.2" to "0.0.3" is appropriate for the addition of the new syncDir functionality.

35-40: LGTM! Well-configured syncDir property.

The syncDir property is correctly configured to enable file stash synchronization:

accessMode: "read" appropriately matches this action's file reading behavior

sync: true enables the synchronization feature as intended by the PR

optional: true maintains backwards compatibility with existing workflows

Integrates well with the existing /tmp file handling logic

components/spotlightr/package.json (1)

3-3: LGTM: Version bump is appropriate.

The version increment from 1.0.0 to 1.0.1 aligns with the addition of the syncDir property to the create-video action.

components/spotlightr/actions/create-video/create-video.mjs (2)

8-8: LGTM: Version bump is consistent.

The version increment matches the package.json update and reflects the addition of the syncDir property.

74-79: LGTM: syncDir property implementation is correct.

The syncDir property is properly configured with:

Type "dir" for directory handling

Read access mode appropriate for file input

Sync enabled for file stash synchronization

Optional flag as expected

This aligns with the PR objectives to enable file sharing between actions via the Connect API.

components/salesforce_rest_api/actions/create-attachment/create-attachment.mjs (1)

21-21: Version increment only – looks good

Patch version 0.5.1 correctly mirrors the component-level bump. No concerns.

components/signnow/package.json (1)

3-3: Version increment looks good.

The version bump aligns with the PR objectives of adding directory synchronization capabilities.

components/signnow/actions/upload-document-with-tags/upload-document-with-tags.mjs (2)

9-9: Version increment is appropriate.

The version bump correctly reflects the addition of new directory synchronization functionality.

18-23: Well-configured syncDir property addition.

The syncDir property is properly configured to enable file stash synchronization:

Correct type (dir) and access mode (read)

Appropriately marked as optional and synchronized

Aligns with the PR objectives for Connect API file sharing between actions

components/the_bookie/package.json (1)

3-3: LGTM: Appropriate version increment

The minor version bump correctly reflects the addition of the new syncDir property to the component's action.

components/the_bookie/actions/create-sales-invoice/create-sales-invoice.mjs (2)

11-11: LGTM: Consistent version increment

The patch version increment appropriately reflects the addition of the new optional property.

72-77: LGTM: Correct syncDir configuration

The syncDir property is properly configured with:

Correct type (dir) for file stash synchronization

Read access mode as appropriate for this action

Optional flag to maintain backward compatibility

Sync flag to enable Connect API integration

This aligns perfectly with the PR objectives for enabling file sharing between separately executed actions.

components/trust/package.json (1)

3-3: Version bump looks good.

The version increment from "0.1.1" to "0.1.2" aligns with the minor changes in this PR.

components/trust/actions/upload-video/upload-video.mjs (2)

9-9: Version bump is consistent.

The version increment aligns with the package.json version bump and the addition of the new syncDir property.

24-29: syncDir property implementation looks good.

The syncDir property is correctly configured with:

type: "dir" for directory handling

accessMode: "read" appropriate for an upload action

sync: true enabling file stash synchronization

optional: true making it non-required

This aligns perfectly with the PR objectives to add directory synchronization capabilities.

components/sonix/package.json (1)

3-3: Version increment looks good.

The version bump from "1.0.0" to "1.0.1" is consistent with the corresponding action file changes and appropriate for adding the new optional syncDir property.

components/sonix/actions/upload-media/upload-media.mjs (2)

10-10: Version increment is consistent.

The version bump matches the corresponding package.json change and is appropriate for the new optional property addition.

62-67: syncDir property implementation looks correct.

The new syncDir property is properly configured with:

Read access mode (appropriate for file uploads)

Optional flag (won't break existing usage)

Sync enabled (supports file stash synchronization)

This aligns with the PR objectives to enable file sharing between separately executed actions via the Connect API.

components/reform/package.json (1)

3-3: LGTM! Appropriate version bump.

The patch version increment aligns with semantic versioning practices for adding optional, backward-compatible functionality (the syncDir property).

components/reform/actions/extract-data-from-document/extract-data-from-document.mjs (1)

10-10: LGTM! Consistent version increment.

The patch version bump is appropriate and consistent with the package.json update.

components/smugmug/package.json (1)

3-3: LGTM! Version bump aligns with action changes.

The version increment from 0.1.0 to 0.1.1 is consistent with the corresponding action file changes that introduce the new syncDir property.

components/smugmug/actions/upload-image/upload-image.mjs (2)

9-9: LGTM! Consistent version increment.

The version bump aligns with the package.json update and reflects the addition of the new syncDir property.

25-30: LGTM! Proper syncDir configuration for file stash synchronization.

The syncDir property is correctly configured with:

type: "dir" for directory input

accessMode: "read" appropriate for an upload action

sync: true to enable stash synchronization

optional: true for backward compatibility

This aligns with the PR objective to enable file sharing between actions via synchronized /tmp directories.

components/scrapfly/package.json (1)

3-3: LGTM: Version bump aligns with action changes.

The minor version increment correctly reflects the addition of the new optional syncDir prop in the associated action.

components/scrapfly/actions/ai-data-extraction/ai-data-extraction.mjs (2)

9-9: LGTM: Version increment is appropriate.

The minor version bump correctly reflects the addition of the new optional syncDir prop.

62-67: LGTM: syncDir prop correctly implements file stash sync capability.

The syncDir prop is properly configured for the file stash sync feature:

type: "dir" enables directory synchronization

accessMode: "read" is appropriate for a data extraction action

sync: true enables File Stash synchronization

optional: true maintains backward compatibility

The prop is not used in the current run logic, which aligns with the PR's objective to add infrastructure for Connect API file stash functionality.

components/shortpixel/package.json (1)

3-3: LGTM! Appropriate version increment.

The minor version bump from 0.1.0 to 0.1.1 correctly reflects the addition of the syncDir property to the optimize-image action.

components/shortpixel/actions/optimize-image/optimize-image.mjs (2)

9-9: LGTM! Consistent version increment.

The version bump from 0.0.1 to 0.0.2 appropriately reflects the addition of the syncDir property.

61-66: Excellent addition! syncDir property aligns perfectly with existing file handling.

The syncDir property is well-configured for file stash synchronization:

Properly typed as "dir" with write access mode

Correctly marked as optional and with sync: true

Aligns perfectly with the existing file writing logic (lines 112-117) that saves optimized images to /tmp

This enables the optimized images written to /tmp to be synchronized across separate action executions via the Connect API, which directly supports the PR's file stash sync objectives.

components/testmonitor/package.json (1)

3-3: Version bump looks correct

Package version correctly increments from 0.1.1 → 0.1.2 to reflect the new action version.

components/testmonitor/actions/create-test-result/create-test-result.mjs (1)

12-12: Action version bump acknowledged

Action version updated to 0.0.3 to match the new prop addition – looks good.

components/whatsapp_business/package.json (1)

3-3: LGTM! Version increment is appropriate.

The version bump from "0.0.11" to "0.0.12" correctly reflects the component updates, specifically the addition of the syncDir property to the send-voice-message action.

components/whatsapp_business/actions/send-voice-message/send-voice-message.mjs (2)

9-9: LGTM! Version increment aligns with the new functionality.

The version bump from "0.0.2" to "0.0.3" appropriately reflects the addition of the syncDir property.

43-48: LGTM! syncDir property correctly configured for file stash synchronization.

The syncDir property is properly defined with:

type: "dir" for directory handling

accessMode: "read" appropriate for this action that reads files for upload

sync: true to enable stash synchronization

optional: true for backward compatibility

This configuration aligns perfectly with the PR objectives to enable file sharing between actions via the Connect API.

components/speechace/package.json (1)

3-3: LGTM! Version bump aligns with action updates.

The patch version increment is appropriate for the addition of optional syncDir props to the speechace actions.

components/speechace/actions/transcribe-and-score-recording/transcribe-and-score-recording.mjs (2)

11-11: LGTM! Version bump is appropriate.

Patch version increment aligns with the addition of the optional syncDir prop.

39-44: LGTM! syncDir prop correctly implements file stash sync requirements.

The syncDir property is properly configured:

Type "dir" for directory handling

Read access mode appropriate for this action

Sync enabled for file stash functionality

Optional to maintain backward compatibility

This aligns perfectly with the PR objectives for enabling file sharing between actions via the Connect API.

components/speechace/actions/score-scripted-recording/score-scripted-recording.mjs (2)

11-11: LGTM! Version bump is appropriate.

Patch version increment aligns with the addition of the optional syncDir prop.

44-49: LGTM! syncDir prop implementation is consistent and correct.

The syncDir property follows the same pattern as the other speechace action:

Proper type "dir" for directory handling

Read access mode appropriate for this action

Sync enabled for file stash functionality

Optional to ensure backward compatibility

This maintains consistency across the speechace component actions while enabling the Connect API file stash synchronization functionality.

components/signaturit/package.json (1)

3-3: LGTM: Appropriate version bump for new functionality.

The patch version increment from 0.2.0 to 0.2.1 correctly follows semantic versioning for the addition of the optional syncDir property to actions.

components/signaturit/actions/create-signature-request-from-template/create-signature-request-from-template.mjs (2)

15-15: LGTM: Appropriate version increment.

The patch version bump from 0.1.0 to 0.1.1 correctly reflects the addition of new optional functionality.

134-139: LGTM: Well-structured syncDir property addition.

The syncDir property is properly configured for file stash synchronization:

type: "dir" correctly indicates directory handling

accessMode: "read" is appropriate for reading files from the synchronized directory

sync: true enables the synchronization feature

optional: true maintains backward compatibility

This aligns perfectly with the PR objective to enable file sharing between actions via the Connect API.

components/signaturit/actions/create-certified-email/create-certified-email.mjs (2)

11-11: LGTM: Appropriate version increment.

The patch version bump from 0.1.0 to 0.1.1 correctly reflects the addition of new optional functionality.

70-75: LGTM: Consistent syncDir property implementation.

The syncDir property configuration is identical to the other action in this component, showing good consistency:

Proper directory type configuration

Read access mode for file synchronization

Optional flag for backward compatibility

Sync enabled for file stash functionality

This implementation supports the PR's file stash synchronization objectives effectively.

components/tinypng/actions/convert-image/convert-image.mjs (1)

11-11: LGTM! Version increment is appropriate.

The version bump reflects the addition of new functionality.

components/syncmate_by_assitro/package.json (1)

3-3: LGTM: Appropriate version bump for new functionality.

The minor version increment correctly reflects the addition of the syncDir property to the component's actions.

components/syncmate_by_assitro/actions/send-bulk-messages/send-bulk-messages.mjs (2)

11-11: LGTM: Version increment reflects new functionality.

The patch version bump appropriately indicates the addition of the syncDir property.

21-26: LGTM: syncDir property correctly implemented.

The syncDir property is properly configured to enable file stash synchronization:

Optional to maintain backward compatibility

Read access mode appropriate for file consumption

Sync enabled for directory synchronization

This aligns perfectly with the PR objectives to enable file sharing between actions via synchronized /tmp directories.

components/syncmate_by_assitro/actions/send-message/send-message.mjs (2)

11-11: LGTM: Consistent version increment.

The patch version bump matches the pattern used in the bulk messages action.

37-42: LGTM: Consistent syncDir implementation.

The syncDir property configuration is identical to the bulk messages action, ensuring consistent behavior across the component. The implementation correctly supports the file stash sync functionality described in the PR objectives.

components/zerobounce/actions/get-validation-results-file/get-validation-results-file.mjs (1)

9-9: Version increment is appropriate.

The version bump from "0.0.1" to "0.0.2" correctly reflects the addition of the syncDir property.

components/roboflow/package.json (1)

3-3: LGTM: Version bump aligns with action updates.

The version increment from 1.0.0 to 1.0.1 correctly reflects the addition of the optional syncDir property to the Roboflow actions in this component.

components/roboflow/actions/upload-image/upload-image.mjs (2)

10-10: LGTM: Version increment reflects new syncDir property.

The version bump to 1.0.1 correctly indicates the addition of the optional syncDir property.

32-37: LGTM: syncDir property correctly configured for file stash synchronization.

The syncDir property is properly configured with:

type: "dir" for directory handling

accessMode: "read" appropriate for file processing

sync: true to enable file stash synchronization

optional: true for backward compatibility

This aligns with the PR objective of enabling file sharing between actions via Connect API.

components/roboflow/actions/classify-image/classify-image.mjs (2)

8-8: LGTM: Version increment consistent with component updates.

The version bump to 1.0.1 aligns with the addition of the syncDir property.

33-38: LGTM: syncDir property consistently implemented.

The syncDir configuration matches the pattern used in other Roboflow actions, ensuring consistency across the component. The read access mode is appropriate for image classification workflows.

components/roboflow/actions/detect-object-from-image/detect-object-from-image.mjs (2)

8-8: LGTM: Version increment completes consistent Roboflow component update.

The version bump to 1.0.1 maintains consistency with other Roboflow actions in this component.

33-38: LGTM: syncDir property implementation completes consistent pattern.

The syncDir configuration is identical to other Roboflow actions, ensuring uniform file stash synchronization capability across the entire component. The read access mode is appropriate for object detection workflows that process image files.

components/tinypng/package.json (1)

3-3: Patch-level bump looks correct
The version increment to 0.2.1 is consistent with the repo-wide pattern of adding the new syncDir prop without breaking changes.

components/signerx/package.json (1)

3-3: LGTM! Version increment follows semantic versioning.

The minor version bump from 0.2.0 to 0.2.1 appropriately reflects the backward-compatible addition of the syncDir property to actions within this component.

components/signerx/actions/upload-package/upload-package.mjs (2)

9-9: LGTM! Version increment is appropriate.

The minor version bump from 0.1.0 to 0.1.1 correctly reflects the addition of the new syncDir property.

23-28: Confirm syncDir usage in upload-package action run

I wasn’t able to locate any reference to the syncDir input inside the run implementation (or even the run function) in components/signerx/actions/upload-package/upload-package.mjs. Please verify whether:

The platform/runner automatically handles the syncDir option

You need to explicitly consume syncDir in the action’s run logic

No code changes until we confirm the intended behavior.

components/youtube_data_api_custom_app/package.json (1)

3-3: LGTM: Appropriate version increment for syncDir property addition.

The version bump from 0.0.7 to 0.0.8 correctly reflects the addition of the optional syncDir property to actions within this component.

components/youtube_data_api/package.json (1)

3-3: LGTM: Proper semantic versioning for optional property addition.

The patch version increment from 1.0.0 to 1.0.1 correctly follows semantic versioning conventions for adding optional functionality.

components/youtube_data_api_custom_app/actions/upload-channel-banner/upload-channel-banner.mjs (2)

9-9: LGTM: Version increment matches property addition.

The version bump from 0.0.2 to 0.0.3 appropriately reflects the addition of the syncDir property.

34-39: LGTM: Correctly configured syncDir property for file stash sync.

The syncDir property is properly configured with:

accessMode: "read" - appropriate for upload actions that read files

sync: true - enables file stash synchronization as intended

optional: true - maintains backward compatibility

components/youtube_data_api_custom_app/actions/upload-thumbnail/upload-thumbnail.mjs (2)

9-9: LGTM: Consistent version increment for syncDir addition.

The version bump from 0.0.1 to 0.0.2 correctly reflects the new syncDir property addition.

40-45: LGTM: syncDir property configured consistently with related actions.

The syncDir property configuration matches the pattern established in other upload actions, ensuring consistent behavior across the component.

components/youtube_data_api/actions/upload-thumbnail/upload-thumbnail.mjs (2)

9-9: LGTM: Semantic versioning applied correctly.

The patch version increment from 1.0.0 to 1.0.1 follows semantic versioning for backward-compatible enhancements.

36-41: LGTM: syncDir property enables file stash synchronization as intended.

The syncDir property implementation aligns perfectly with the PR objectives to enable file sharing between actions via the /tmp directory synchronization.

components/youtube_data_api/actions/upload-video/upload-video.mjs (2)

9-9: LGTM: Appropriate version bump.

The patch version increment correctly reflects the addition of a new optional property.

55-60: LGTM: Well-configured syncDir property.

The syncDir property is properly configured for file stash synchronization:

accessMode: "read" is appropriate for upload actions that need to read files

optional: true maintains backward compatibility

sync: true enables the intended file stash functionality

Placement at the end of props follows good practice

This aligns perfectly with the PR objective to enable file sharing between actions via /tmp directory synchronization.

components/youtube_data_api_custom_app/actions/upload-video/upload-video.mjs (2)

9-9: LGTM: Consistent version increment.

The version bump appropriately reflects the addition of the new optional syncDir property.

63-68: LGTM: Consistent syncDir implementation.

The syncDir property configuration is identical to the standard YouTube Data API component, ensuring consistency across related components. The configuration is appropriate for this upload action's file handling requirements.

components/youtube_data_api/actions/upload-channel-banner/upload-channel-banner.mjs (2)

9-9: LGTM: Appropriate version increment.

The patch version bump correctly reflects the addition of the new optional syncDir property.

30-35: LGTM: Consistent syncDir pattern maintained.

The syncDir property follows the same configuration pattern as other YouTube Data API upload actions, ensuring consistency across the component. The read access mode is appropriate for this banner upload action that needs to read image files from the synchronized directory.

components/tinypng/actions/compress-image/compress-image.mjs (1)

8-8: LGTM: Appropriate version increment.

The patch version increment from "1.0.0" to "1.0.1" is appropriate for adding an optional property without breaking changes.

components/sendgrid/package.json (1)

3-3: Version increment looks good.

The version bump from 0.5.0 to 0.5.1 is appropriate for the addition of the syncDir property to the SendGrid actions.

components/sendgrid/actions/send-email-multiple-recipients/send-email-multiple-recipients.mjs (2)

13-13: Version increment is appropriate.

The version bump from 0.1.0 to 0.1.1 correctly reflects the addition of the new syncDir property.

147-152: Verify property naming consistency

The PR description refers to adding a dir property, but this action defines it as syncDir. Please double-check across all updated components that you’ve intentionally used syncDir here (and aren’t relying on a plain dir property elsewhere).

• File: components/sendgrid/actions/send-email-multiple-recipients/send-email-multiple-recipients.mjs
• Lines: 147–152

components/sendgrid/actions/send-email-single-recipient/send-email-single-recipient.mjs (2)

11-11: Version increment is consistent.

The version bump from 0.1.0 to 0.1.1 is consistent with the other SendGrid action and appropriate for the property addition.

168-173: Consistent implementation across SendGrid actions.

The syncDir property configuration is identical to the multiple recipients action, ensuring consistency within the SendGrid component. The property is correctly configured for file stash synchronization with read access mode.

components/ringcentral/package.json (1)

3-3: Version bump LGTM
0.5.0 → 0.5.1 aligns with the new syncDir prop in the download-recording action. No other concerns.

components/what_are_those/package.json (1)

3-3: Minor version bump acknowledged
0.1.1 → 0.1.2 correctly reflects the action updates.

components/ramp/package.json (1)

3-3: Version bump verified
0.2.0 → 0.2.1 matches the added syncDir support in upload-receipt.

components/xero_accounting_api/package.json (1)

3-3: Version increment confirmed
0.3.0 → 0.3.1 in line with action updates; no additional issues observed.

components/ringcentral/actions/download-recording/download-recording.mjs (1)

8-8: LGTM! Appropriate syncDir configuration for download action.

The version increment and syncDir property addition are correctly implemented. The write access mode aligns perfectly with this action's functionality of downloading recordings and writing them to the /tmp directory.

Also applies to: 49-53

components/supabase/actions/batch-insert-rows/batch-insert-rows.mjs (1)

9-9: LGTM! Well-configured syncDir for CSV file reading capability.

The version increment and syncDir property are properly implemented. The read access mode is appropriate for this action's CSV file processing functionality, and the optional: true flag ensures backwards compatibility.

Also applies to: 30-35

components/transifex/actions/upload-file/upload-file.mjs (1)

8-8: LGTM! Correct syncDir configuration for file upload action.

The version increment and syncDir property are appropriately implemented. The read access mode matches the action's need to read files for upload, and the optional: true flag maintains backwards compatibility.

Also applies to: 60-65

components/transifex/actions/download-file/download-file.mjs (1)

8-8: LGTM! Proper syncDir implementation for file download action.

The version increment and syncDir property are correctly configured. The write access mode is appropriate for this action's functionality of downloading files and writing them to the /tmp directory.

Also applies to: 18-22

components/xero_accounting_api/actions/upload-file/upload-file.mjs (1)

12-12: LGTM! Well-implemented syncDir for file upload functionality.

The version increment and syncDir property are correctly configured. The read access mode aligns with the action's file upload requirements, and the optional: true flag ensures backwards compatibility with existing file path/URL usage patterns.

Also applies to: 48-53

components/wordpress_org/actions/upload-media/upload-media.mjs (2)

9-9: Version increment looks good.

The minor version bump from 0.0.2 to 0.0.3 appropriately reflects the addition of the new syncDir property.

40-45: Correctly configured syncDir for upload action.

The syncDir property is properly configured with "read" access mode since this action reads files to upload them to WordPress. Making it optional ensures backward compatibility.

components/vapi/actions/upload-file/upload-file.mjs (2)

9-9: Consistent version increment.

The version bump from 0.0.2 to 0.0.3 aligns with the pattern across other components in this PR.

18-23: Consistent syncDir implementation for upload action.

The configuration matches the pattern established in other upload actions, with appropriate "read" access mode and optional flag.

components/raindrop/actions/parse-bookmark-file/parse-bookmark-file.mjs (2)

9-9: Appropriate patch version increment.

The version bump from 1.0.0 to 1.0.1 is suitable for adding an optional property without breaking changes.

18-23: Correctly configured for file parsing.

The "read" access mode is appropriate for this parsing action that needs to read bookmark files from the synchronized directory.

components/rapid_url_indexer/actions/download-project-report/download-project-report.mjs (2)

9-9: Version increment is appropriate.

The version bump from 0.0.1 to 0.0.2 correctly reflects the addition of the new syncDir property.

23-27: syncDir definition is consistent across all actions

Every action in the codebase—whether it reads from or writes to /tmp—defines a required syncDir property without an optional flag. The download-project-report action follows this established pattern, so there’s no inconsistency to address.

Likely an incorrect or invalid review comment.

components/sharepoint/actions/download-file/download-file.mjs (2)

8-8: Consistent version increment.

The version bump from 0.0.2 to 0.0.3 follows the pattern established across other components in this PR.

42-46: Consistent with other write actions.

The syncDir property uses appropriate "write" access mode for this download action. The required (not optional) nature is consistent with the rapid_url_indexer download action, suggesting a pattern where write actions require synchronized directories.

components/rendi/actions/run-ffmpeg-command/run-ffmpeg-command.mjs (3)

11-11: Version increment is appropriate.

The version bump from 0.0.1 to 0.0.2 correctly reflects the addition of the syncDir functionality.

43-47: Proper syncDir implementation.

The syncDir property is correctly configured with write access mode and synchronization enabled, which aligns with the PR's objective to enable file stash sync functionality.

101-102: Excellent implementation of dynamic file path.

The code properly uses the STASH_DIR environment variable when available, falling back to /tmp. This correctly implements the stash sync functionality described in the PR objectives.

components/xero_accounting_api/actions/download-invoice/download-invoice.mjs (2)

9-9: Version increment is appropriate.

The version bump from 0.2.0 to 0.2.1 correctly reflects the addition of the syncDir functionality.

55-57: Good addition of filePath in return value.

Returning the filePath is a useful enhancement for downstream action consumption.

components/twilio/actions/download-recording-media/download-recording-media.mjs (3)

11-11: Version increment is appropriate.

The version bump from 0.1.6 to 0.1.7 correctly reflects the addition of the syncDir functionality.

66-68: Good filePath validation logic.

The logic to ensure the file path starts with /tmp is a good safety measure.

74-76: Good addition of filePath in return value.

Returning the filePath is a useful enhancement for downstream action consumption.

components/todoist/package.json (1)

3-3: Appropriate version increment.

The version bump from 0.2.0 to 0.2.1 correctly reflects the minor functionality additions (syncDir properties) to actions within this component.

components/ragie/package.json (1)

3-3: Appropriate version increment.

The version bump from 0.2.0 to 0.2.1 correctly reflects the minor functionality additions (syncDir properties) to actions within this component.

components/slack/package.json (1)

3-3: LGTM - Appropriate version bump for additive feature.

The patch version increment correctly reflects the addition of the syncDir property to Slack actions without introducing breaking changes.

components/trello/package.json (1)

3-3: LGTM - Consistent version increment pattern.

The patch version bump appropriately reflects the addition of syncDir properties to Trello actions while maintaining backward compatibility.

components/ramp_sandbox/package.json (1)

3-3: LGTM - Proper semantic versioning.

The patch version increment correctly reflects the additive nature of the syncDir feature addition to Ramp Sandbox actions.

components/sftp/package.json (1)

3-3: LGTM - Appropriate version management.

The patch version increment correctly reflects the addition of directory synchronization capabilities to SFTP actions without breaking existing functionality.

components/todoist/actions/export-tasks/export-tasks.mjs (2)

10-10: LGTM - Appropriate version increment.

The patch version bump correctly reflects the additive nature of the syncDir property addition.

20-24: LGTM - Well-implemented syncDir property.

The syncDir property is correctly configured for this export action:

type: "dir" properly defines it as a directory sync property

accessMode: "write" is appropriate since this action exports/writes CSV files

sync: true enables the file stash synchronization as intended by the PR objectives

This implementation aligns perfectly with the goal of enabling file sharing between separately executed actions via the Connect API.

components/todoist/actions/import-tasks/import-tasks.mjs (2)

9-9: Version increment looks good.

Appropriate patch version bump for the syncDir feature addition.

26-31: syncDir property implementation is correct.

The syncDir property is properly configured with read access mode, which aligns with this action's need to read CSV files for task import. The optional flag ensures backward compatibility.

components/trello/actions/create-card/create-card.mjs (2)

10-10: Version increment is appropriate.

Proper patch version bump for the syncDir feature addition.

154-159: syncDir property correctly implemented.

The syncDir property with read access mode is well-suited for this action since it handles file attachments. The optional nature ensures backward compatibility.

components/ramp_sandbox/actions/upload-receipt/upload-receipt.mjs (2)

9-9: Version increment follows proper semantic versioning.

Appropriate patch version bump for the new syncDir functionality.

30-35: syncDir property properly configured.

The read access mode is appropriate for this file upload action that needs to read receipt files from the synchronized directory.

components/slack/actions/upload-file/upload-file.mjs (2)

11-11: Version increment is correct.

Proper patch version bump for adding the syncDir functionality.

35-40: syncDir property implementation is consistent.

The read access mode is well-suited for this file upload action. The optional nature maintains backward compatibility while enabling directory synchronization for file sharing between actions.

components/ramp/actions/upload-receipt/upload-receipt.mjs (2)

9-9: Version increment is appropriate.

Correct patch version bump for the syncDir feature addition.

30-35: syncDir property correctly implemented.

The read access mode is appropriate for this file upload action. The consistent implementation across the Ramp components (base and sandbox) ensures proper functionality.

components/ragie/actions/create-document/create-document.mjs (2)

9-9: LGTM: Appropriate version increment.

The patch version bump correctly reflects the additive nature of the syncDir property addition.

51-56: LGTM: Well-structured syncDir property.

The syncDir prop is properly configured with read access mode and sync enabled, which aligns perfectly with the PR's objective to enable file stash synchronization for actions that handle file operations.

components/what_are_those/actions/grade-sneakers-condition/grade-sneakers-condition.mjs (2)

9-9: LGTM: Consistent version increment.

The version bump follows the same pattern as other actions in this PR.

53-58: LGTM: Consistent syncDir implementation.

The syncDir property configuration matches the established pattern across all updated actions, ensuring consistency in the file stash synchronization feature.

components/ragie/actions/update-document-file/update-document-file.mjs (2)

9-9: LGTM: Consistent versioning within ragie component.

The version increment matches the sibling create-document action, maintaining consistency across the ragie component.

32-37: LGTM: Standard syncDir configuration.

The syncDir property follows the same pattern as other file-handling actions, ensuring consistent behavior across the platform.

components/what_are_those/actions/identify-sneakers-from-photo/identify-sneakers-from-photo.mjs (2)

9-9: LGTM: Consistent version increment.

The version bump aligns with the other what_are_those action, maintaining component-level consistency.

18-23: LGTM: Proper syncDir implementation.

The syncDir property is correctly configured for this image processing action, following the established pattern across all updated actions.

components/trello/actions/add-attachment-to-card/add-attachment-to-card.mjs (2)

9-9: LGTM: Appropriate patch version increment.

The version bump correctly reflects the non-breaking addition of the syncDir property.

56-61: LGTM: Well-implemented syncDir property.

The syncDir configuration is consistent with all other actions in this PR and appropriate for an action that handles file attachments.

components/sftp/actions/upload-file/upload-file.mjs (2)

10-10: Appropriate version increment for new optional property.

The version bump from 0.4.0 to 0.4.1 is appropriate for adding a new optional property without breaking changes.

31-36: syncDir property correctly defined but not yet utilized.

The syncDir property is correctly defined with:

type: "dir" for directory synchronization

accessMode: "read" appropriate for reading from file stash

sync: true to enable synchronization

optional: true for backward compatibility

However, the property is not used in the run method. Based on the PR objectives, this appears to be intentional as part of adding the infrastructure for file stash synchronization across actions.

components/what_are_those/actions/find-sneakers-by-sku/find-sneakers-by-sku.mjs (2)

9-9: Appropriate version increment for new optional property.

The version bump from 0.0.2 to 0.0.3 correctly follows semantic versioning for adding a new optional property.

18-23: syncDir property consistently defined across components.

The syncDir property definition is identical to other actions in this PR, maintaining consistency:

Correct directory type configuration

Read access mode suitable for accessing shared file stash

Optional flag ensures backward compatibility

The property is not yet utilized in the logic, which aligns with the PR's phased approach to adding file stash synchronization infrastructure.

components/tinypng/actions/convert-image/convert-image.mjs

components/zerobounce/actions/get-validation-results-file/get-validation-results-file.mjs

components/tinypng/actions/compress-image/compress-image.mjs

components/xero_accounting_api/actions/download-invoice/download-invoice.mjs

components/twilio/actions/download-recording-media/download-recording-media.mjs

js07 marked this pull request as ready for review July 1, 2025 16:29

coderabbitai bot reviewed Jul 1, 2025

View reviewed changes

js07 merged commit 68a3ffe into master Jul 1, 2025
11 checks passed

js07 deleted the configure-filesync-for-components-q-z branch July 1, 2025 17:07

coderabbitai bot mentioned this pull request Jul 2, 2025

Configure file stash sync: Happy Scribe-Puppeteer #17373

Merged

This was referenced Jul 30, 2025

Browserless - update base_url #17880

Merged

[BUG] Fix packages with Import failure #17881

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Configure file stash sync: Ragie-Zoho WorkDrive #17375

Configure file stash sync: Ragie-Zoho WorkDrive #17375

Uh oh!

js07 commented Jun 30, 2025 •

edited by coderabbitai bot

Loading

Uh oh!

vercel bot commented Jun 30, 2025

Uh oh!

coderabbitai bot commented Jun 30, 2025 •

edited

Loading

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

Uh oh!

coderabbitai bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Configure file stash sync: Ragie-Zoho WorkDrive #17375

Configure file stash sync: Ragie-Zoho WorkDrive #17375

Uh oh!

Conversation

js07 commented Jun 30, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

WHY

Summary by CodeRabbit

Uh oh!

vercel bot commented Jun 30, 2025

Uh oh!

coderabbitai bot commented Jun 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram(s)

Poem

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

js07 commented Jun 30, 2025 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Jun 30, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)