Release v1.2.0, via minor release #5118
Assignees
Comments
2 tasks
conorsch
added a commit
that referenced
this issue
Mar 5, 2025
## Describe your changes Built from head on web repo 68a1cd50391197ee180af9966e474e04363c50f8. Tested locally, and I see the new version displayed in my local browser, in the footer. ## Issue ticket number and link No specific issue, updating opportunistically. Towards #5118. ## Testing and review We don't have automated tests to ensure the version spec, so I already confirmed locally that the appropriate commit has is referenced. Therefore, as long as CI is green on this PR, we're good to go. ## 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: > no changes to consensus logic, only updated a GUI frontend
2 tasks
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, let's prepare a
v1.2.0release, flushing out the current contents of the main branch.Changes to include
ClientStatusandConsensusStateWriteExtin ibc component #5111Compatibility
As this is a minor 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/v1.1.0..main
The text was updated successfully, but these errors were encountered: