Release v1.0.0 🎉

[conorsch]

Tooling Release

We plan to publish all of the workspace crates (#4988), to unblock external developers. As part of that work, we're updating several critical dependencies, and intend to bump crate versions to 0.82.x to denote the changes. Despite the minor version bump, we must execute this change while maintaining full compatibility with the existing protocol, so that nodes can upgrade seamlessly.

Changes to include

• The dependency bumps, particularly of tonic, in penumbra: update ecosystem tendermint/ibc crates #4980
• The crate renaming and workspace-publishing logic in feat: publish workspace crates #4986
• Everything already on main, and/or in the 0.81.x release series

Workflow implications

The currently active version of Penumbra protocol is 9, with crate version 0.81.0: https://github.com/penumbra-zone/penumbra/blob/v0.81.0/COMPATIBILITY.md The most recent tagged release was v0.81.0, although we intend to continue to update this release series (#4988). In order to maintain velocity on 0.81.x while preparing changes for 0.82.x in parallel, I propose the following:

1. revert changes to main in penumbra: update ecosystem tendermint/ibc crates #4980, thereby restoring the main branch to an immediately shippable state, including numerous fixes to pindexer
2. proceed with release of 0.81.1 as described in Release v0.81.1, via point-release #4988
3. recreate the dedicated feature branch release/v0.82.x, based on the 0.81.1 tag, and resubmit Release v0.81.1, via point-release #4988 & feat: publish workspace crates #4986 into it.

The proposal above essential re-implements the steps initially taken by @erwanor (and @SuperFluffy) in #4973 & #4975. However, given the breakage we discovered post-merge, it's valuable to recreate the release/v0.82.x branch based on the refactored changesets in those PRs.

The release/v0.82.x branch will quickly get out of sync with the main as changes are made towards the 0.81.x series. Once we start creating tags on the release/v0.82.x, we cannot rebase it, without breaking those tags. Therefore we'll need to cherry-pick frequently if we want to make changes across both release series. We'll try to minimize the amount of time we're maintaining both branches.

Post-QA, when the team deems the 0.82.x changes ready, we can prepare a changeset to reconcile with main, as we did with #4969.

Compatibility

Although this is a minor-release, all changes must be fully compatible for all nodes and clients. Therefore we must perform careful assurance work to ensure there are no breaking changes:

• publish alpha tags to crate.io, so that external developers can evaluate depending on them
• update external tooling to consume those published dependencies (e.g. hermes)
• publish beta tag for use in upgrading PL testnet
• upgrade PL testnet to beta tag, performing serial upgrades, so that we can observe nodes on both 0.81.x and 0.82.x versions interacting, to confirm that consensus is maintained

Ongoing work will continue to target main.

[conorsch]

We've discussed internally, and decided to publish the workspace crates as v1.0.0. We'll forego the 0.82.x series entirely.

[conorsch]

The tag for v1.0.0 is live, but the release workflows are currently failing, due to upstream breakage. When that's resolved, I'll rerun the workflows, so that we have a public release object to point to, as well as prebuilt binaries available for download, as usual.

[duckinator]

@conorsch we just sorted everything out on cargo-dist's end, so you should be good to go. Thanks again for letting us know about it! 🙂

[conorsch]

Thanks, @duckinator, for the extremely prompt support—and for a fantastic project in cargo-dist!

After rerunning the workflow, we have a final release object for v1.0.0: https://github.com/penumbra-zone/penumbra/releases/tag/v1.0.0