chore: cut 0.7.0 - #73
Merged
Merged
Conversation
Four badge features and a fix have landed since v0.6.0. One of them changes what a badge's key names, so a config written for 0.6.0 draws no badges and says nothing about it. The release notes carry that as the only warning anyone gets. The README's pointer to docs/configuration.md said badges are drawn from bead metadata, which is narrower than the truth now. The README at the squash is this version's crates.io page for ever, so it is fixed here rather than after.
The sentence defining the new key rule gave external_ref and a metadata key the same treatment, which reads as though bdi recognises the second name. It recognises no service at all. The two halves now say where each name comes from: bd writes the field names, and the reader writes everything under metadata.
The highlights explained each change instead of naming it. A reader of the notes has not seen the config surface, so the detail taught them nothing and buried the one edit they owe. Four bullets say what a badge can do now. Reading any field of a bead is one of them rather than a warning, because that is what the change is. Upgrading is its own section and one sentence.
A cut badge keeps its underline and stays clickable, so somebody moving from 0.6.0 to 0.7.0 sees no change in how one is drawn. The notes say nothing about it in either direction. Upgrading says what changed before what to do about it, so a reader knows why the edit is owed.
GraemeF
enabled auto-merge (squash)
September 11, 2026 09:19
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.
The badge key change breaks every config written for 0.6.0. The notes'
Upgradingsection is the only warning anyone gets: A badge key now names a field of a bead, so putmetadata.in front of every one in your config.The notes say nothing about the cut-badge fix in pull request 74, which this branch carries. At
v0.6.0a cut badge was already drawn underlined with its link dropped, so somebody moving from 0.6.0 to 0.7.0 sees no change in how one is drawn. Being able to open it is new. That is left out on purpose.The README's pointer to
docs/configuration.mdsaid badges are drawn from bead metadata, which pull request 72 made narrower than the truth. The README at the squash is this version's crates.io page for ever, so it is fixed here rather than afterwards.