chore(release): v0.17.0 - #24
Merged
Merged
Conversation
Minor bump: #23 adds a feature (a global config at ~/.config/forge.toml), so the workspace version moves 0.16.0 -> 0.17.0 under semver. Tagging v0.17.0 after this lands fires release.yml, which builds frg-macos-aarch64.tar.gz + SHA256SUMS -- the artifacts ferrosa-workbench's stage-payload downloads to pin the installer's bundled forge.
Merged
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.
Minor bump so a stable forge release exists carrying #23.
#23 added a feature — a global config at
~/.config/forge.toml— so under semver the workspace version moves 0.16.0 → 0.17.0. Same shape as #22 (chore(release): v0.16.0): the workspaceversionin Cargo.toml plus Cargo.lock churn, nothing else.Why now
The Ferrosa AI installer pins its bundled binaries to stable releases, and forge's newest stable is v0.16.0, which predates #23. Until a stable release exists, no installer can ship the global-config support.
What happens after this merges
Tagging
v0.17.0firesrelease.yml, which buildsfrg-macos-aarch64.tar.gz+SHA256SUMS— the exact assetsferrosa-workbench'smake stage-payloaddownloads and checksum-verifies.Not merging this myself: standing rule is no auto-merge on public repos.