release: cut v0.5.8 - #984
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Version bump only: 0.5.7 → 0.5.8 across the 13 sites the release asserts, plus the v0.5.8 release notes.
Cargo.toml[workspace.package].version(1)Cargo.lockworkspace crate entries (5, name-anchored: maxplayer, maxplayer-core, maxplayer-desktop, maxplayer-evals, maxplayer-relay-write-policy)npm/*/package.jsonversions (4) and the launcher'soptionalDependenciespins (3)RELEASE_NOTES.md— a new## v0.5.8section prepended; the v0.5.7 section is byte-identical below itNo source change. 7 files, 58 insertions, 13 deletions.
Two deliberate non-edits, both verified:
crates/buzz/Cargo.lockis untouched. Its only0.5.7is the third-party cratefixedbitset.Cargo.lockalready contained one0.5.8— the third-party cratederanged— so the lockfile edit is anchored on the crate NAME rather than the version string, andderangedis byte-identical after the bump.Release notes lead with the platform fee, since that is what changes for an operator who upgrades: 10% of the offer amount is now charged at collect and paid automatically to a compiled-in Lightning address. The notes also state plainly that no test exercises the live remit path.