Repository navigation
Conversation
This branch has not been deployed
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 the reviewed release notes required before tagging v0.4.0-beta.1. The notes describe the first beta's worktree/PR workflows, safer mutation outcomes, expanded harness guidance, compatible guidance updates, and Homebrew/native Linux distribution. The migration section highlights execution by default and use of --dry-run for previews.
The release inventory came from gha release create-notes since v0.3.0-alpha's publication timestamp and was checked against the 51-commit range. Administrative changes were omitted; user-facing changes and the human contributor are linked. README wording now covers prereleases, and manual install examples target the beta assets.
Validation: local build passed, git diff --check passed, architecture refresh produced no record changes, and committed architecture-check passed. Default-branch Go CI and package installation passed after PR #32. This PR changes documentation only. The release remains unpublished; after merge, run the guarded release dry-run from the exact default-branch tip, publish, then verify all downloads and the Homebrew update. Repository rules require an approving review before merge.