Prepare 0.63.2 release #3393
Merged
Prepare 0.63.2 release #3393
Conversation
This file contains 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
There are two changes here:
1. Ensure that the PENUMBRA_VERSION is submitted to remote repo build
jobs, so that a matching container version is created, e.g.
"ghcr.io/penumbra-zone/galileo:penumbra-v0.63.1".
2. Ensure that the PENUMBRA_VERSION var is populated when bouncing
the deployment on the cluster, so the newly created tag is
referenced.
Crucially, we needed to switch from "repository_dispatch" events (which
support a `client_payload` dict in the posted JSON) to
"workflow_dispatch" events (which support an `inputs` dict, allowing us
to set the required `penumbra_version` field).
Refs #3279.
(cherry picked from commit 80401e3)
In this commit we move from cargo-dist 0.0.4 to 0.4.2. The tooling updates are considerable, as the version number implies. To test, I regenerated the workflow YAML and run it many times in a private fork of the repo. With the notable change that we're no longer building binaries for Windows (#3298), everything else looks to work pretty well. Even better, the runtime for the workflow has decreased from ~60m to ~20m, with the biggest win skipping Windows builds. Refs #3279, #3298. (cherry picked from commit ed6ced1)
In the future, once the MemoView has an AddressView, we can change this to show the AddressView and show the address structure. (cherry picked from commit a041ea4)
Since we moved to new pcli config file in #3239, we don't use the archives anymore. If a machine doesn't have archive dirs, then pcli will throw an error, which is bad. Stop looking for archive dirs. Similar, we shouldn't look for a custody.json file, we should look for the new config.toml file. Closes #3321. (cherry picked from commit f839582)
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.
This PR prepares the upcoming
v0.63.2point release. See context in #3182 (comment). As described there, most of these changes are CI related, geared toward providing working binary builds again. There are also two (2) QoL pcli improvements.After this PR is merged into the
release/0.63.xbranch, the usualcargo releasesteps will be performed on that branch, including a tag, to trigger the point release.