release: prepare the reviewed 0.1.0 first-public-release unlock - #79
Open
CompleteDotTech wants to merge 4 commits into
Open
release: prepare the reviewed 0.1.0 first-public-release unlock#79CompleteDotTech wants to merge 4 commits into
CompleteDotTech wants to merge 4 commits into
Conversation
…ernance evidence Prepare the OpenCoven#41 release authorization record with the decision marked pending fresh maintainer authorization: fixed-group version 0.1.0, the four-package set with dev-cli deferred (OpenCoven#37/OpenCoven#57), the Node/OS/architecture matrix, launch criteria, and a rollback owner proposal. Gather governance prerequisite evidence from repository config, workflow files, live read-only GitHub API state (protected npm-release environment with required reviewers), and the maintainer's recorded 2026-08-28 audit, and list every item that requires maintainer confirmation. No external mutation is authorized.
Run the canonical 'pnpm release:version' on the fixed group: the two pending changesets (the OpenCoven#68 managed-native custody summary and the empty bootstrap placeholder) are consumed, the four release packages stay at exactly 0.1.0 with exact workspace:0.1.0 internal ranges, and the managed-native custody and browser-safe subpath summaries are folded into the '## 0.1.0' changelog entries of @opencoven/sdk-core and @opencoven/cave-client so the first published release notes describe everything 0.1.0 ships. No version bump is pending after this commit.
Deliberately open the repository publication lock for the 0.1.0 first public release: release.config.json sets publishingEnabled to true and the four release package manifests become publishable, while the second, independent deployment lock (the protected npm-release environment approval), the OIDC id-token/attestation requirements, the prepublishOnly authorization gate, and the no-token-fallback rule are preserved unchanged. Update the tests that pinned the closed state to pin the reviewed open state instead (readiness summary, publish-path gating, artifact-before-npm ordering, token-fallback rejection, both sides of the privacy lock), and align the README and RELEASING.md release-status language. This change activates nothing: no tag, no publish, no dispatch.
Write the exact operator procedure for the annotated sdk-v0.1.0 tag at the reviewed commit, release-workflow verify mode, artifact retention and digest comparison with the reviewed candidate, and the registry-unchanged proof, with every external action behind an explicit authorization stop. Document the authorization-gated continuation (issue steps 5-7: one-time bootstrap publish, trusted publishing, registry/provenance validation) with acceptance checks, record the reviewed candidate artifact digests and the local non-mutating dry-run evidence, and state the master authorization sentence. No tag was created and no workflow was dispatched.
This was referenced Aug 30, 2026
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
1 participant
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.
Recreated from CompleteDotTech/sdk#5 as a delta-only branch against current upstream
main(66edd4d). The separate security-review document from fork PR #1 is intentionally carried by upstream #76, and the fork-onlyworkflow_dispatchbootstrap was omitted.This preparatory artifact advances #41: it records the pending authorization decision, folds the two pre-release changesets into the fixed 0.1.0 changelogs, opens the repository publication lock while preserving protected-environment/OIDC/prepublish gates, and adds the no-publish rehearsal runbook. Nothing is tagged, published, unlocked externally, or dispatched by this PR.
Dependencies remain explicit: #74 for the conformance/release contract and #76 for the security review. Because #74 is an open parallel evolution of the release configuration, this branch is intentionally based on current
main; it must be rebased and conflict-reviewed after #74 merges before release approval.Validation: the changed release/readiness/policy suites pass 35/35 locally (with the repository's required Node 24.18.0-24.x range to be enforced by CI);
git diff --checkis clean. The authorization record explicitly remains pending fresh maintainer authorization.