release: v4.0.0-alpha.51 - #228
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
4.0.0-alpha.51on npm's existingnextchannel, including the sync self-update planning fix from #227. The kit's own release cache is refreshed before planning; failed lookups retain eligible cached evidence without renewing its timestamp.Only the package version changes. The source fix passed all 15 applicable checks in #227. All 48 focused sync/version tests pass on this version, and the packed CLI reports alpha.51 and loads
--help --all. This PR reruns CI before the annotated tag triggers the repository's publication workflow. Published artifact integrity/content and the installed CLI will be verified afterward.