chore: bump platform libraries version

[hbjORbj]

Published ✅

[coderabbitai]

Walkthrough

This pull request updates a dependency in apps/api/v2/package.json, changing @calcom/platform-libraries from version 0.0.349 to 0.0.350 in the dependencies section. No other files or configurations are modified.

Possibly related PRs

• chore: bump platform libs to 0.0.338 #23589: Also updates the @calcom/platform-libraries dependency in apps/api/v2/package.json, bumping its version in the same location.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

Pre-merge checks (2 passed, 1 inconclusive)

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	The current pull request description “Published ✅” does not provide any meaningful information about the version bump or related changes and is too generic to confirm that it relates to the dependency update in this changeset.	Please update the pull request description to clearly summarize the dependency bump, reference the updated @calcom/platform-libraries version change, and remove any placeholder text (e.g., “Fixes CAL-[FILL IN]”) so that reviewers can understand the purpose of this PR at a glance.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title “chore: bump platform libraries version” directly and succinctly captures the primary change in the pull request, namely updating the @calcom/platform-libraries dependency version. It is clear, concise, and follows conventional commit style, making it easy for team members to understand the main purpose of the PR at a glance. There is no unrelated information or unnecessary detail, and the title accurately reflects the changes in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-platform-libraries-version

---

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: 0

🧹 Nitpick comments (1)

apps/api/v2/package.json (1)

12-18: Double-check workspace vs npm alias resolution for @calcom/platform-libraries
Dependencies in apps/api/v2/package.json use the npm: protocol, while your dev scripts invoke the local workspace—this can lead to duplicate installs or version drift. Verify how Yarn actually resolves this by inspecting your declaration and lockfile:

grep -R '"@calcom/platform-libraries"' -n apps/api/v2/package.json
yarn workspaces list --json | jq '.[] | select(.name=="@calcom/platform-libraries")'
yarn why @calcom/platform-libraries
grep -R '@calcom/platform-libraries@' -n yarn.lock

If you intend to track the published package at runtime, keep npm: and add a comment explaining this choice. If you want local linking during development, switch the dependency to workspace:* for consistency.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2cc8b1c and c34056e.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• apps/api/v2/package.json (1 hunks)

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

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Detect changes

🔇 Additional comments (1)

apps/api/v2/package.json (1)

41-41: Upgrade verified: @calcom/platform-libraries@0.0.350 present, no stale 0.0.349 refs, and lockfiles clean.

[github-actions]

E2E results are ready!

• Workflow #77077.1 latest results