Repository navigation
chore: release 0.43.0 on npm next (refs #2874) - #2876
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
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.
Release 0.43.0 publishes the changes merged since v0.42.0 through the existing GitHub release workflow to npm
next. npmlatestremains 0.42.0; this release does not promote it.Includes the exact eight V1 evidence files generated from live Git/GitHub/npm authorities, synchronized version surfaces, reviewed changelog and the version-anchored npm README. Scope includes project catalog policy, editable Root context, task storage and dormant preflight settings, installer opt-in, configuration regression checks, and keyboard/status-strip fixes. Incomplete integrations and pending manual keyboard verification are stated in the notes.
Validation: live candidate evidence verified twice, SHA256SUMS, version synchronization, package dry run/pack and diff checks. Full CI is required via
ci:full; publication waits for the final merged-commit verification.Closes #2874.