Release v0.81.1, via point-release #4988
Assignees
Comments
github-actions
bot
added
the
needs-refinement
conorsch
removed
the
needs-refinement
This was referenced Jan 16, 2025
Closed
See more recent discussion in #4991. In short, we plan to keep the main branch consistent with the 0.81.x release series, and we'll move anything 0.82-related to its own feature branch. That'll allow us to maintain velocity on current development while also performing next-up QA on the testnet. |
conorsch
added a commit
that referenced
this issue
Jan 17, 2025
This reverts commit 64c32ef, which constitutes the squash-merge of PR #4980. We're backing this change out strictly to simplify release engineering: we want the `main` branch to remain fully compatible with the `0.81.x` series, and we'll continue QA of significant version changes in a parallel release branch, `release/v0.82.x`. I'll handle preparing the latter shortly. See related discussion in #4988 & #4991.
2 tasks
conorsch
added a commit
that referenced
this issue
Jan 17, 2025
) ## Describe your changes This reverts commit 64c32ef, which constitutes the squash-merge of PR #4980. We're backing this change out strictly to simplify release engineering: we want the `main` branch to remain fully compatible with the `0.81.x` series, and we'll continue QA of significant version changes in a parallel release branch, `release/v0.82.x`. I'll handle preparing the latter shortly. ## Issue ticket number and link See related discussion in #4988 & #4991. ## Testing and review This is a programmatic change, in that I simply ran `git revert 64c32ef`, wrote some notes into the commit message, and pushed it up. I also made sure to rerun `just proto` to regenerate the protos, and confirmed there are no changes. That's good, that's precisely what we wanted to see. Preferably this change would land before #4992, since #4992 changes protos. I'll regenerate protos in 4992 on top of this once it lands on main. ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > This commit is expressly intended to preserve protocol compatibility with 0.81.x. Future work on QA to ensure compat with 0.82 will happen in a separate branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tooling Release
In order to ship some minor improvements and bug fixes, let's prepare a
v0.81.1release.Changes to include
subaccountfilter to theOwnedPositionIdsrpc #4985 -> protos(view): add a subaccount filter to theOwnedPositionIdsrpc #4992Compatibility
As this is a point-release, all changes must be fully compatible for all nodes and clients.
Careful attention should be given to the delta between most recent tag on the main branch:
https://github.com/penumbra-zone/penumbra/compare/v0.81.0..main
Given that we've merged #4980, we should use a release branch to add to the
v0.81.xrelease series, without shipping those dep bumps. Sort out the release branches and make sure only the minimal set of changes is included, rather than flushing out all of main, as is usual for a point-release.The text was updated successfully, but these errors were encountered: