ci: two-stage release with manual approval (3.x)#816
Conversation
Replace the previous shared node-release reusable workflow with the same prepare + approve + release flow used on master: a manually dispatched Prepare Release opens a version-bump PR, and merging it triggers a Release that checks the version against npm, pushes an approval request to DingTalk, waits on the `release` environment gate, then publishes (dist-tag `latest-3`) via OIDC and creates the GitHub Release.
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Brings the 3.x maintenance branch onto the same release flow as master (#814), so every line releases the same way.
Flow: run Prepare Release (manual, with a version) -> it opens a
release/vX.Y.ZPR -> merge it -> Release checks the version against npm, pushes an approval request to DingTalk, waits on thereleaseenvironment gate, then publishes and creates the GitHub Release.3.x specifics:
latest-3(neverlatest).prepublishOnly) on Node 22.node-releasereusable workflow.id-token: write).Requires the repo
releaseenvironment (required reviewers) and npm trusted-publisher config to allow this branch's workflow. DingTalk secrets are already set repo-wide.