-
Notifications
You must be signed in to change notification settings - Fork 126
docs(l1,l2): improve release process docs second step #5265
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR improves the release process documentation by expanding the "Bump version" step with more detailed and precise instructions.
- Clarifies that both
[workspace.package]version and three additional standaloneCargo.tomlfiles need to be updated - Adds explicit instructions to run
cargo updatein all affected workspaces - Includes the previously missing
quote-genworkspace in the list
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - root `Cargo.lock` | ||
| - `sp1/Cargo.lock` | ||
| - `risc0/Cargo.lock` | ||
| After updating the version in the `Cargo.toml` files, we need to update the `Cargo.lock` files to reflect the new versions. Run `cargo tree` in their respective directories: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does cargo tree update the lockfile?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's even safer than cargo update because it doesn't update dependencies that you don't want to be updated.
|
We should also add a step changing the version in the CLI reference docs ( |
**Motivation** The second step of the release process docs was missing some details. **Description** - Clarify which `Cargo.toml` file versions need to be bumped. - Specify to run `cargo update` in the corresponding workspaces. - Add `quote-gen` workspace to the list of workspaces to bump.
Motivation
The second step of the release process docs was missing some details.
Description
Cargo.tomlfile versions need to be bumped.cargo updatein the corresponding workspaces.quote-genworkspace to the list of workspaces to bump.