release: prepare Phase 1 Experimental 0.4.3 - #211
Merged
Merged
Conversation
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.
Rationale
Prepare the next coherent Phase 1 Experimental candidate from the changes merged since
v0.4.2. This keeps Phase 0 Stable0.3.2on npmlatestand publishes0.4.3only through the protectedexperimentalworkflow.Tracks #210. The release issue remains open until protected publication and public smoke are complete.
Release contents
Validation
npm ci --ignore-scriptsnpm run buildandnpm run check:skillsnpm testnpm run validate:acceptancenpm run validate:p0npm run validate:p1 -- --require-publish-readynpm run validate:release -- --tag v0.4.3npm run test:artifactsnpm run test:p1-exact-artifactsnode scripts/verify-experimental-release.mjs --phase candidate --jsonAll five
0.4.3npm versions are currently unused. Registry dist-tags remainlatest=0.3.2andexperimental=0.4.2before publication. Localnpm trust listverification requires an authenticated npm owner session and returned 401; the protected tag must not be created until the five Trusted Publisher records are verified.