Skip to content

docs: Clarify stable and canary release processes in documentation #6206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nikosdouvlis
Copy link
Member

@nikosdouvlis nikosdouvlis commented Jun 27, 2025

Description

Updates the CICD docs to reflect the latest state of the release process.

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Documentation
    • Expanded and clarified the CI/CD documentation for stable and canary release processes.
    • Provided detailed, step-by-step descriptions of actions performed during each release.
    • Updated references to manual updates and direct commits, directing users to private repository documentation where appropriate.

@nikosdouvlis nikosdouvlis requested a review from bratsos June 27, 2025 13:06
Copy link

changeset-bot bot commented Jun 27, 2025

⚠️ No Changeset found

Latest commit: cbccc16

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Jun 27, 2025

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

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2025 1:06pm

Copy link
Contributor

coderabbitai bot commented Jun 27, 2025

📝 Walkthrough

Walkthrough

The documentation for the CI/CD workflow was updated to provide more detailed and structured explanations of both stable and canary release processes. The stable release section now explicitly lists the automated actions performed after merging the version bump PR, including publishing SDKs, updating the clerkjs-proxy worker, updating the dashboard's @clerk/nextjs version, and updating generated docs. References to manual PR updates were removed and replaced with a pointer to private repository documentation. The canary release section was revised to specify the actions taken on each commit to main, such as dispatching the worker update workflow and deploying the canary Accounts project, while removing references to direct commits and redundant workflows. No changes were made to exported or public entities.


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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
docs/CICD.md (3)

12-18: Reduce repetition & improve readability in the bullet list

The phrase “A workflow dispatch will be triggered to update …” is repeated three times, making the list verbose. You can shorten each bullet to start with the affected repo while keeping the parallel structure.

- A workflow dispatch will be triggered to update the `clerkjs-proxy` worker in `clerk/sdk-infra-workers`.
- A workflow dispatch will be triggered to update the `@clerk/nextjs` version in `clerk/dashboard`.
- A workflow dispatch will be triggered to update the generated docs in `clerk/generated-typedoc`.
+ Dispatch workflows to:
+ - update the `clerkjs-proxy` worker (`clerk/sdk-infra-workers`)
+ - bump `@clerk/nextjs` in the dashboard (`clerk/dashboard`)
+ - regenerate and publish docs (`clerk/generated-typedoc`)

This keeps the bullets concise while preserving the same meaning.


19-22: Link wording & private-repo reference

“For details regarding the package versioning/publishing process” → “For details on package versioning and publishing”. Slight tightening avoids the double gerund.

Also, consider explicitly calling out that the linked worker docs are private, e.g. “(private, internal)”, so external contributors immediately know access is restricted.


25-29: Fix typos and duplicated sentence

  1. Missing article: “every time a PR is merged”.
  2. Word split: “fol lowing”.
  3. The first and second sentences convey the same trigger; merging them removes redundancy.
-A canary release will be triggered every time PR is merged into `main`. Every commit merged into main will trigger the fol lowing actions:
+A canary release is triggered on every commit merged into `main`; it performs the following actions:

This clarifies the trigger condition and fixes the typo.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d898eb7 and cbccc16.

📒 Files selected for processing (1)
  • docs/CICD.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.md`: Follow all instructions, patterns and conventions that are defined in these MD files.

**/*.md: Follow all instructions, patterns and conventions that are defined in these MD files.

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

  • docs/CICD.md
🧠 Learnings (2)
📓 Common learnings
Learnt from: dstaley
PR: clerk/javascript#6116
File: .changeset/tangy-garlics-say.md:1-2
Timestamp: 2025-06-13T16:09:53.061Z
Learning: In the Clerk JavaScript repository, contributors create intentionally empty changeset files (containing only the YAML delimiters) when a PR touches only non-published parts of the codebase (e.g., sandbox assets). This signals that no package release is required, so such changesets should not be flagged as missing content.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/development.mdc:0-0
Timestamp: 2025-06-23T12:25:30.457Z
Learning: Follow the established PR template, include tests for all new features, update documentation for API changes, and ensure all CI checks pass before merging.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-06-23T12:25:40.214Z
Learning: Release management is automated with Changesets, using semantic versioning and coordinated releases to maintain compatibility between packages.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/global.mdc:0-0
Timestamp: 2025-06-23T12:25:34.662Z
Learning: Development workflow requires making changes in the relevant package under packages/, using playground apps for testing, and following established testing and documentation requirements.
docs/CICD.md (9)
Learnt from: dstaley
PR: clerk/javascript#6116
File: .changeset/tangy-garlics-say.md:1-2
Timestamp: 2025-06-13T16:09:53.061Z
Learning: In the Clerk JavaScript repository, contributors create intentionally empty changeset files (containing only the YAML delimiters) when a PR touches only non-published parts of the codebase (e.g., sandbox assets). This signals that no package release is required, so such changesets should not be flagged as missing content.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-06-23T12:25:40.214Z
Learning: Release management is automated with Changesets, using semantic versioning and coordinated releases to maintain compatibility between packages.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/development.mdc:0-0
Timestamp: 2025-06-23T12:25:30.457Z
Learning: Follow the established PR template, include tests for all new features, update documentation for API changes, and ensure all CI checks pass before merging.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/development.mdc:0-0
Timestamp: 2025-06-23T12:25:30.457Z
Learning: Maintain comprehensive JSDoc comments for all public APIs to improve documentation and developer experience.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/global.mdc:0-0
Timestamp: 2025-06-23T12:25:34.662Z
Learning: Development workflow requires making changes in the relevant package under packages/, using playground apps for testing, and following established testing and documentation requirements.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-06-23T12:25:40.214Z
Learning: All packages are published under the @clerk namespace on npm, ensuring consistent naming and discoverability.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/global.mdc:0-0
Timestamp: 2025-06-23T12:25:34.662Z
Learning: All packages published from this repository must use the @clerk namespace.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-06-23T12:25:40.214Z
Learning: Framework packages depend on @clerk/clerk-js for core functionality, while @clerk/shared and @clerk/types provide common utilities and TypeScript definitions used across packages.
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-06-23T12:25:40.214Z
Learning: Environment variables prefixed with CLERK_* and NEXT_PUBLIC_CLERK_* are supported for configuration across different environments.
🪛 LanguageTool
docs/CICD.md

[uncategorized] ~16-~16: The official spelling of this programming framework is “Next.js”.
Context: ...ispatch will be triggered to update the @clerk/nextjs version in clerk/dashboard. - A work...

(NODE_JS)


[uncategorized] ~28-~28: The official spelling of this programming framework is “Next.js”.
Context: ...ng the most recent @canary version of @clerk/nextjs. This happens for testing purposes. F...

(NODE_JS)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: Build Packages
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep/ci

Copy link

pkg-pr-new bot commented Jun 27, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6206

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6206

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6206

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6206

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6206

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6206

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6206

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6206

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6206

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6206

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6206

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6206

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6206

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6206

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6206

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6206

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6206

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6206

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6206

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6206

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6206

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6206

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6206

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6206

commit: cbccc16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants