From 08e61e67556b1d217026ea997b5969c7c0819101 Mon Sep 17 00:00:00 2001 From: tiennm99 Date: Wed, 21 Oct 2026 17:52:56 +0700 Subject: [PATCH] docs: refresh Cargo.lock in the release dry-run steps --- docs/release-process.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/release-process.md b/docs/release-process.md index 2f649cc..65da842 100644 --- a/docs/release-process.md +++ b/docs/release-process.md @@ -127,9 +127,11 @@ public Releases feed and does not reach any client, legacy or Tauri. keeps the tag push from starting a publishing run; never use a plain `vX.Y.Z` tag for a dry run, because pushing it publishes a release marked latest. -2. On a scratch branch, set `Cargo.toml` `version` to `0.0.0-test` and - commit. The tag check also runs for drafts, so the tag must point at a - commit whose `Cargo.toml` version matches it. +2. On a scratch branch, set `Cargo.toml` `version` to `0.0.0-test`, run + `cargo build` locally to refresh `Cargo.lock`, and commit both files. + The release jobs build with `--locked`, so a stale `Cargo.lock` fails + them before any draft exists. The tag check also runs for drafts, so + the tag must point at a commit whose `Cargo.toml` version matches it. 3. Tag that commit and push the tag, then start the "Release" workflow from the Actions tab (`workflow_dispatch`) with that tag as input. 4. Check the draft: it must hold exactly the six assets in the table