release: prepare the reviewed 0.1.0 first-public-release unlock - #5
Closed
CompleteDotTech wants to merge 4 commits into
Closed
release: prepare the reviewed 0.1.0 first-public-release unlock#5CompleteDotTech 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.
CompleteDotTech
marked this pull request as ready for review
August 30, 2026 11:21
Owner
Author
|
Recreated upstream as OpenCoven#79: OpenCoven#79. Closing this duplicate fork PR; review continues upstream. |
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.
Summary
Preparatory review artifact for OpenCoven#41 (first public release, version 0.1.0). It completes work-plan items 1-5 on a branch stacked on
security/first-release-review-40:docs/release/sdk-0.1.0-release-authorization-record.md): names the exact fixed-group version 0.1.0, the four-package set with@opencoven/dev-clideferred ([SDK 0.1.0][P0] Resolve CLI scope and implement native trust boundaries OpenCoven/sdk#37/build: defer private CLI from SDK 0.1 release OpenCoven/sdk#57), the supported Node/OS/architecture matrix, launch criteria, and a rollback-owner proposal. The decision itself is marked pending fresh maintainer authorization.pnpm release:versionrun consumed the two pending pre-release changesets; the managed-native custody and browser-safe subpath summaries are folded into the## 0.1.0changelog entries of@opencoven/sdk-coreand@opencoven/cave-client. Versions stay pinned at exactly0.1.0with exactworkspace:0.1.0internal ranges; no version bump is pending.release.config.jsonsetspublishingEnabledtotrueand the four release manifests become publishable. The independent deployment lock (protectednpm-releaseenvironment approval), OIDCid-token/attestationspermissions, theprepublishOnlyauthorization gate, and the no-token-fallback rule are preserved unchanged. Tests that pinned the closed state now pin the reviewed open state (both sides of the privacy lock, artifact-before-npm ordering, token-fallback rejection). Nothing is activated: no tag, no publish, no release-workflow dispatch.docs/workflows/first-release-rehearsal-runbook.md): the no-publish operator procedure — annotatedsdk-v0.1.0tag at the reviewed commit, release-workflow verify mode, artifact retention, registry-unchanged proof, digest comparison with the reviewed candidate — plus the authorization-gated continuation (issue steps 5-7: one-time bootstrap publish, trusted publishing, registry/provenance validation) with per-step authorization stops and the master authorization sentence. Reviewed-candidate digests are recorded and confirmed reproducible at this head.Authorization status: pending fresh maintainer authorization. Nothing external has been tagged, published, unlocked, or dispatched; the OpenCoven#38/F-1 platform-record gap (Chat schema-v2 records on darwin-arm64 / linux-x64 / win32-x64) remains unresolved until a maintainer resolves or formally waives it.
Assignee: @CompleteDotTech
Advances OpenCoven#41 (gates OpenCoven#42/OpenCoven#44 and OpenCoven#31 closure)
Stacked on fork PR #1 (security/first-release-review-40): merge #1 first. After #1 merges upstream, rebase this branch onto origin/main and flip this PR base to main — the upstream compare then shows only the delta.
Stacked upstream compare (delta view for review): https://github.com/OpenCoven/sdk/compare/main...CompleteDotTech:sdk:release/sdk-0.1.0-unlock-41?expand=1
Validation
tests/release-readiness.spec.ts,tests/package-manifests.spec.ts, andtests/release-policy.spec.tsupdated with the lock change (58 test files / 1215 tests pass locally, +2 net over the parent head).corepack pnpm@10.34.0 verifypasses (exit 0 on head d792b4a: typecheck, clean public dist, build + tests, verify:contracts, verify:package, verify:release, coverage, multi-seed stress, lint) andgit diff --checkis clean.## 0.1.0entries instead, so no version bump is pending (repository-maintenance changes need no changeset per.changeset/README.md).Release impact
Opens the repository publication lock for the 0.1.0 first public release as a reviewable change while preserving the fail-closed two-key design: activation additionally requires the protected
npm-releaseenvironment approval, the maintainer-authorizedsdk-v0.1.0tag, and a release-workflow dispatch frommain. Compatibility: none (no code or API change; versions unchanged at 0.1.0). Migration: none.