Repository navigation
chore(ore-rs): release v0.9.0-rc.1 (pre-release) - #102
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-plz-2026-10-10T22-40-06Z
branch
from
October 12, 2026 08:35
2a97616 to
2c39662
Compare
Pre-release for testing with external projects before 0.9.0. - Version 0.9.0-rc.1 instead of 0.9.0. - release-plz: git_release_type = "auto", so the GitHub release is marked as a pre-release. - cliff.toml: the changelog template had no version heading, so every release since 0.3.0 was appended under [Unreleased]. It now writes '## [version] - date'. This release gets its own section, and the earlier un-headed entries are grouped under '[0.8.4] and earlier'.
coderdan
approved these changes
Oct 12, 2026
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.
🤖 New release (pre-release)
ore-rs: 0.8.4 -> 0.9.0-rc.1A pre-release for testing with external projects before 0.9.0. Cargo won't pick a pre-release for
0.8or0.9requirements, so a project only gets it by pinning it:ore-rs = "=0.9.0-rc.1". The Bit6 and chained wire formats aren't frozen yet, so don't store their ciphertexts.Edits on top of the generated release (a0b26a7):
0.9.0-rc.1instead of0.9.0.release-plz.toml:git_release_type = "auto", so the GitHub release is marked as a pre-release.cliff.toml: the changelog template now writes a## [version] - dateheading. Previously every release since 0.3.0 was appended under[Unreleased].CHANGELOG.mdnow has a section for this release, and the earlier entries are grouped under[0.8.4] and earlier.Merge this PR before anything else lands on
main. A push tomainmakes release-plz regenerate this branch, which would discard these edits.This PR was generated with release-plz and edited by hand.