-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Publish dry-run #2004
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a PR changes a crate's version, we should try a dry-run publish to make sure it'll actually work (we'll have to figure out how to handle the fact that we may be releasing multiple crates at the same time). This'll catch issues where, e.g., we cut a release of some crate A (e.g., the FVM) but fail to cut a release of a dependency (e.g., the blockstore) blocking the FVM release (because the FVM crate depends on some unreleased blockstore change).
The text was updated successfully, but these errors were encountered: