Repository navigation
chore: release v0.1.2 - #3
Merged
Merged
Conversation
The about page renders `mxmon {CARGO_PKG_VERSION}`, so `settings_about`
froze the version at whatever it was when captured (0.1.1). Every release
bump then broke the golden the moment the version moved, which is exactly
what happened on the v0.1.2 release PR: identical code passed CI on main
(0.1.1) but failed on the PR (0.1.2). Filter the version to `mxmon X.Y.Z`
alongside the existing clock filter so the frame is stable at any version.
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.
🤖 New release
mxmon: 0.1.1 -> 0.1.2Changelog
This PR was generated with release-plz.