Increment Zoho Desk component versions

[verhovsky]

I forgot to do this in #18708

Summary by CodeRabbit

• Chores
  • Bumped version metadata across multiple Zoho Desk actions and event sources, and updated the Zoho Desk package version.
  • No functional, behavioral, or API changes.
  • Existing integrations and workflows remain unaffected.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs-redirect-do-not-edit	Ignored			Oct 15, 2025 9:47pm

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible
• Create subscription webhooks sources (vs polling sources) whenever possible
• Always emit a summary with events
• Use a built-in deduping strategy wherever possible
• When building webhook sources, follow these best practices
• When building polling sources, follow these best practices

[coderabbitai]

Walkthrough

This PR updates only exported metadata version strings across multiple Zoho Desk actions and sources; there are no changes to logic, control flow, method signatures, or behavior.

Changes

Cohort / File(s)	Summary of changes
Zoho Desk Actions: version bumps components/zoho_desk/actions/add-ticket-attachment/add-ticket-attachment.mjs, components/zoho_desk/actions/add-ticket-comment/add-ticket-comment.mjs, components/zoho_desk/actions/create-account/create-account.mjs, components/zoho_desk/actions/create-contact/create-contact.mjs, components/zoho_desk/actions/create-ticket/create-ticket.mjs, components/zoho_desk/actions/find-contact/find-contact.mjs, components/zoho_desk/actions/find-or-create-contact/find-or-create-contact.mjs, components/zoho_desk/actions/search-ticket/search-ticket.mjs, components/zoho_desk/actions/send-email-reply/send-email-reply.mjs, components/zoho_desk/actions/update-contact/update-contact.mjs, components/zoho_desk/actions/update-ticket/update-ticket.mjs	Bumped exported version fields only (examples: 0.0.4→0.0.5, 0.1.3→0.1.4). No logic, API, or control-flow changes.
Zoho Desk Sources: version bumps components/zoho_desk/sources/changed-ticket-status/changed-ticket-status.mjs, components/zoho_desk/sources/deleted-article-instant/deleted-article-instant.mjs, components/zoho_desk/sources/new-account/new-account.mjs, components/zoho_desk/sources/new-agent/new-agent.mjs, components/zoho_desk/sources/new-article-instant/new-article-instant.mjs, components/zoho_desk/sources/new-contact/new-contact.mjs, components/zoho_desk/sources/new-ticket-attachment/new-ticket-attachment.mjs, components/zoho_desk/sources/new-ticket-comment/new-ticket-comment.mjs, components/zoho_desk/sources/new-ticket-message/new-ticket-message.mjs, components/zoho_desk/sources/new-ticket/new-ticket.mjs, components/zoho_desk/sources/updated-article-instant/updated-article-instant.mjs, components/zoho_desk/sources/updated-ticket/updated-ticket.mjs, components/zoho_desk/package.json	Bumped exported version fields only (examples: 0.0.5→0.0.6, 0.0.1→0.0.2, 0.1.0→0.1.1, package 0.2.2→0.2.3). No logic, API, or control-flow changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I hopped through files with a twitching nose,
Pasted new numbers where metadata grows.
No logic shaken, no flows undone,
Just tidy bumps—one by one.
A rabbit's nod: the version race is run. 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is largely incomplete and does not follow the required template structure. The template specifies a "WHY" section that should be completed by the author, but the provided description consists only of a single sentence: "I forgot to do this in #18708". This brief reference to another PR offers no substantive explanation of why the version increments were necessary or what the actual changes accomplish. While the statement is on-topic, the description lacks the required detail and template adherence expected for a complete pull request submission.	The author should expand the pull request description to include the required "WHY" section from the template. They should explain the rationale behind the version increments—whether these are patch, minor, or major version bumps and what triggered the need for them. Additionally, a brief explanation of the scope of changes (e.g., which components were updated) would help reviewers better understand the context and intent of the pull request.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Increment Zoho Desk component versions" is clear, concise, and directly summarizes the primary change in the changeset. The raw summary confirms that all modified files involve bumping version numbers across multiple Zoho Desk action and source modules, as well as the package.json file, which perfectly aligns with the title. The title is specific enough for a teammate to quickly understand the nature of the changes without being overly detailed.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 123b1c6 and 1591e0c.

📒 Files selected for processing (1)

• components/zoho_desk/package.json (1 hunks)

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

• components/zoho_desk/package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

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

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}