Onlyoffice docs link updates

[GTFalcao]

Requested by OnlyOffice, docs were updated. Can merge after approving, no need for QA

Summary by CodeRabbit

• Documentation

  • Updated documentation links for Create Room, Invite User, Upload File actions, and New File/New Folder/New User events to point to current API backend usage pages.

• Chores

  • Bumped versions for the OnlyOffice DocSpace component and related actions/sources; no changes to runtime behavior or user-facing functionality.

[vercel]

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

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Nov 3, 2025 6:30pm
pipedream-docs-redirect-do-not-edit	Ignored			Nov 3, 2025 6:30pm

[coderabbitai]

Walkthrough

This PR updates OnlyOffice Docspace component metadata: documentation URLs in descriptions now point to new API-backend/usage-api paths, and several component versions (actions, sources, package) are incremented. No functional logic or control flow changes.

Changes

Cohort / File(s)	Summary
Actions metadata updates components/onlyoffice_docspace/actions/create-room/create-room.mjs, components/onlyoffice_docspace/actions/invite-user/invite-user.mjs, components/onlyoffice_docspace/actions/upload-file/upload-file.mjs	Description URLs updated to new API-backend/usage-api paths; versions bumped (create-room & invite-user 0.0.2→0.0.3, upload-file 0.1.2→0.1.3).
Sources metadata updates components/onlyoffice_docspace/sources/new-file/new-file.mjs, components/onlyoffice_docspace/sources/new-folder/new-folder.mjs, components/onlyoffice_docspace/sources/new-user-added/new-user-added.mjs	Description URLs updated to new API-backend/usage-api paths; versions bumped 0.0.1→0.0.2.
Package version components/onlyoffice_docspace/package.json	Package version bumped from 0.2.1 to 0.2.2.

Sequence Diagram(s)

(omitted — changes are metadata-only and do not modify control flow)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Homogeneous metadata edits across multiple files.
• Pay extra attention to:
  • components/onlyoffice_docspace/package.json (version consistency).
  • Action/source files to ensure only description/version fields changed and no accidental code edits.

Poem

🐰 I hopped through docs and changed a line,
Links rerouted, versions align.
No logic altered, just tidy and bright,
A tiny bump, then off I bite—
Hooray for metadata done just right! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The pull request description is minimal and lacks the required 'WHY' section from the template, providing only a brief statement without detailed context.	Add a 'WHY' section explaining the rationale for these documentation updates and any impact on users or the system.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating OnlyOffice documentation links across multiple components and actions.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch onlyoffice-docs-link-updates

---

📜 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 02eaeb9 and b01b5a2.

📒 Files selected for processing (1)

• components/onlyoffice_docspace/sources/new-folder/new-folder.mjs (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• components/onlyoffice_docspace/sources/new-folder/new-folder.mjs

---

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.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7f7145f and 02eaeb9.

📒 Files selected for processing (7)

• components/onlyoffice_docspace/actions/create-room/create-room.mjs (1 hunks)
• components/onlyoffice_docspace/actions/invite-user/invite-user.mjs (1 hunks)
• components/onlyoffice_docspace/actions/upload-file/upload-file.mjs (1 hunks)
• components/onlyoffice_docspace/package.json (1 hunks)
• components/onlyoffice_docspace/sources/new-file/new-file.mjs (1 hunks)
• components/onlyoffice_docspace/sources/new-folder/new-folder.mjs (1 hunks)
• components/onlyoffice_docspace/sources/new-user-added/new-user-added.mjs (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-01-23T03:55:15.166Z

Learnt from: GTFalcao
Repo: PipedreamHQ/pipedream PR: 15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.

Applied to files:

• components/onlyoffice_docspace/sources/new-file/new-file.mjs

⏰ 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). (4)

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

🔇 Additional comments (7)

components/onlyoffice_docspace/package.json (1)

3-3: LGTM! Package version bumped appropriately.

The version increment aligns with the metadata updates across component files.

components/onlyoffice_docspace/sources/new-file/new-file.mjs (1)

8-9: LGTM! Metadata updated appropriately.

Documentation URL migrated to the new API backend path and version incremented.

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

7-8: LGTM! Documentation and version updated correctly.

The description now points to the new API backend documentation path, and the version has been incremented appropriately.

components/onlyoffice_docspace/actions/invite-user/invite-user.mjs (1)

6-7: LGTM! Metadata updated to reference new documentation.

Documentation URL has been migrated to the API backend usage path, and version incremented.

components/onlyoffice_docspace/sources/new-folder/new-folder.mjs (1)

9-9: Version update looks good.

components/onlyoffice_docspace/sources/new-user-added/new-user-added.mjs (1)

7-8: LGTM! Documentation URL and version updated appropriately.

Metadata changes align with the OnlyOffice documentation migration to the new API backend structure.

components/onlyoffice_docspace/actions/create-room/create-room.mjs (1)

6-7: Documentation URL verified and accessible.

The new OnlyOffice API backend documentation URL (https://api.onlyoffice.com/docspace/api-backend/usage-api/create-room/) returns HTTP 200, confirming it is accessible and points to the correct resource. Version has been appropriately incremented to 0.0.3.