Conversation
# Conflicts: # CHANGELOG.md
Prepare 0.5.1 release
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.
Now that 0.5.1 is tagged, published, and released, this brings the release commit back onto
developso the two branches stop diverging. It is the last step of the release checklist and carries nothing that was not already reviewed in #117.Summary
Synchronize the completed BREOS 0.5.1 release from
mainback intodevelop.This carries only the reviewed release metadata from PR #117:
0.5.1dated 2026-08-11Unreleasedchangelog section closed as[0.5.1] - 2026-08-11No source, simulation, or public result changes.
Release outcome
breos 0.5.1published via trusted publishing and verified by a clean-environment installv0.5.1points at62ab4f4onmain