chore(release): 0.3.2-beta.1 - #188
Merged
Merged
Conversation
A pre-release because the asset rename it carries is an experiment: only a published release can show whether installers pick the unsuffixed archive, and a prerelease tag moves no floating tag while it does.
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.
A pre-release rather than 0.3.2, because the change it exists to carry is an experiment.
Why a pre-release
The self-contained archive becomes the unsuffixed asset (#185), and whether that actually makes mise pick it is not knowable from the repository — asset selection is a property of the installer, resolved against a published release. This tag produces one. If the selection still lands on
-fxdep, the naming gets another pass before anything is promoted.The tag is safe to publish because
release.ymltreats a hyphenated version as a pre-release throughout: the GitHub Release is marked as such, the container's floatinglatest/vX.Y/aottags stay on 0.3.1, and the NuGet package inherits a prerelease suffix sodotnet tool installskips it unless asked. The v0.3.0 betas established the path.Contents
No new features — the issue backlog is empty. One behavioural fix to the binary (
--versionand--helpno longer print scenario warnings) and the distribution work: the asset rename, the two AUR packages,SHA256SUMS, and the install guide.Also
[Unreleased]had accumulated two separate### Fixedblocks from incremental edits; the release section merges them and orders Added / Changed / Fixed.After this ships
Two things that need a published release and are deliberately not in this PR: measuring what mise picks from the renamed assets, and pointing both AUR PKGBUILDs at a version whose asset names match the new scheme. AUR submission waits for the stable 0.3.2 — a prerelease is the wrong thing to hand a distribution.