release: bootstrap inert release control plane - #33
Draft
ntanwir10 wants to merge 2 commits into
Draft
Conversation
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Bootstrap the reviewed release control plane onto
mainwhile every publication authority remains inert. This makes the default-branch workflows available for later provider onboarding and rehearsals without changing the public product version or starting a release.Provenance and scope
ae98219e10d0f0bf9118c0ed00b024f429fea3e7(main)eb3adbe99b62614b000cb17e7802c11331afc3d0cli/package.jsonandcli/package-lock.jsonremain at public version1.0.5..release-please-manifest.jsonis neutral at1.0.5; Release Please is separately gated byRELEASE_PLEASE_ENABLED.Safety changes
v*tag trigger and its direct npm/GitHub publishers.Current closed posture
RELEASE_AUTOMATION_ENABLED=falsewas rechecked before push.RELEASE_PLEASE_ENABLEDandRELEASE_PROVIDER_REHEARSAL_ENABLEDare absent, which is fail-closed for their== 'true'guards.release-ledgerbranch contains onlyactive-versions.jsonwith an emptytrainsarray.v1.0.5.Verification
1.0.5application typecheck and build pass locally.git diff --checkpasses.Review checklist
1.0.5is unchanged in package metadata and the Release Please manifest.Do not merge this PR until its exact head is green and the bootstrap review is complete. Merging this PR is not authority to enable automation, configure providers, mark PR #32 ready, create a candidate tag, or publish anything.