Repository navigation
chore(release): prepare FAT 2.0.1 - #109
Merged
Merged
Conversation
Synchronize workspace and runtime-data versions, asset names, citation metadata, and the source-install tag. Add release notes and finalize the changelog for the installer and firmware extraction fixes so users can retry with matching binary downloads.
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.
The published 2.0.0 downloads predate the installer fixes in #107 and firmware extraction fixes in #108. This prepares FAT 2.0.1 so issue reporters can retry those changes with a versioned binary and matching runtime data.
Validation on the release worktree:
cargo fmt --all --checkcargo clippy --workspace --all-targets --all-features --locked -- -D warningscargo test --workspace --locked -- --test-threads=1: 1,996 passed, 0 failed, 1 ignored local-fixture testdist generate --checkanddist plan: passed; five native platforms plannedThe Release workflow must pass its five native builds and archive smoke checks before tagging and publication.