build: track upstream main branch, not tag #18
Merged
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.
The testnet release process involves updating Galileo's Cargo.toml for the most recent testnet tag. While it's grand to have a 1:1 correspondence between Galileo's deps and the testnet version it handles disbursements for, it's quite tedious to bump the deps every week. Let's try tracking main branch, instead. Ultimately we aim to automate the build and rollout of galileo updates, but for now, a human's attention is still required.
We aren't committing
Cargo.lock
in this repo (should we?), so no diff for that file. Towards #17.