From 846f198fd6ef42ba4e43abe3dcadbb27a2be488c Mon Sep 17 00:00:00 2001 From: M3gA-Mind Date: Fri, 23 Oct 2026 23:27:47 +0530 Subject: [PATCH] ci(release): bump the workspace tinyflows requirement with the crate version The release step rewrote only crates/tinyflows/Cargo.toml. The root workspace dependency every sibling crate inherits pins tinyflows = { version = "0.8.0", path = ... }, so a minor bump to 0.9.0 no longer matched it and `cargo update --precise` failed to resolve. Rewrite that requirement in the same step, assert it took, and include the root manifest in the release commit. --- .github/workflows/release.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 45b1c19c..8a30649f 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -112,6 +112,11 @@ jobs: # of the root manifest) — the released package's own manifest is # the one that carries a version to bump. perl -0pi -e 's/(\[package\][\s\S]*?\nversion = ")[^"]+(")/$1$ENV{NEXT_VERSION}$2/' crates/tinyflows/Cargo.toml + # The workspace dependency every sibling crate inherits pins a + # version too; left behind, a minor or major bump no longer matches + # it and `cargo update --precise` cannot resolve. + perl -pi -e 's/^(tinyflows = \{ version = ")[^"]+(", path = "crates\/tinyflows" \})/$1$ENV{NEXT_VERSION}$2/' Cargo.toml + grep -qx "tinyflows = { version = \"${NEXT_VERSION}\", path = \"crates/tinyflows\" }" Cargo.toml cargo update -p "$CRATE_NAME" --precise "$NEXT_VERSION" - name: Commit version bump and tag @@ -121,7 +126,7 @@ jobs: run: | git config user.name "github-actions[bot]" git config user.email "41898282+github-actions[bot]@users.noreply.github.com" - git add crates/tinyflows/Cargo.toml Cargo.lock + git add Cargo.toml crates/tinyflows/Cargo.toml Cargo.lock git commit -m "Release ${RELEASE_TAG}" git tag -a "${RELEASE_TAG}" -m "Release ${RELEASE_TAG}"