release: v4.0.0-alpha.50 - #226
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.
Prepare
4.0.0-alpha.50on the existingnextprerelease channel. This release includes qualified host health checks and explicit provider connection testing from #225, plus the ADR-0051 publication correction.Update the package's single version source and ADR-0053 release bookkeeping. This does not graduate the project to beta or stable.
Validation: 77 focused health tests passed. The packed CLI reports the new version, loads
--help --all, and contains the health backend and dashboard modules. Candidate tarball SHA-256:cd5170732730f8213665757875657495d6bf2276a3b0de699e0138391c933cce. All source-change CI checks passed on #225; this release PR runs the matrix again before tagging. Publication will use the repository's tag-triggered release workflow, followed by registry integrity/content verification.