Skip to content

Conversation

@ilitteri
Copy link
Contributor

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.

@ilitteri ilitteri self-assigned this Nov 11, 2025
Copilot AI review requested due to automatic review settings November 11, 2025 04:22
@ilitteri ilitteri requested a review from a team as a code owner November 11, 2025 04:22
@github-actions github-actions bot added L1 Ethereum client L2 Rollup client labels Nov 11, 2025
Copilot finished reviewing on behalf of ilitteri November 11, 2025 04:23
Copy link
Contributor

Copilot AI left a 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 standalone Cargo.toml files need to be updated
  • Adds explicit instructions to run cargo update in all affected workspaces
  • Includes the previously missing quote-gen workspace in the list

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ilitteri ilitteri enabled auto-merge November 11, 2025 13:25
- 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:
Copy link
Collaborator

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?

Copy link
Contributor Author

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.

@github-project-automation github-project-automation bot moved this to In Review in ethrex_l1 Nov 11, 2025
@ilitteri ilitteri added this pull request to the merge queue Nov 11, 2025
@ManuelBilbao
Copy link
Contributor

We should also add a step changing the version in the CLI reference docs (CLI.md file)

@ilitteri ilitteri removed this pull request from the merge queue due to a manual request Nov 11, 2025
@ilitteri ilitteri enabled auto-merge November 11, 2025 14:37
@ilitteri ilitteri added this pull request to the merge queue Nov 11, 2025
Merged via the queue into main with commit 9a4a69b Nov 11, 2025
39 checks passed
@ilitteri ilitteri deleted the fix_release_process_docs branch November 11, 2025 15:13
@github-project-automation github-project-automation bot moved this from In Review to Done in ethrex_l1 Nov 11, 2025
xqft pushed a commit that referenced this pull request Nov 11, 2025
**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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

L1 Ethereum client L2 Rollup client

Projects

Status: Done
Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants