From 58d76fea55703f1bf75f1fa481172d9e831b1e65 Mon Sep 17 00:00:00 2001 From: changepacks Date: Tue, 8 Sep 2026 11:50:41 +0000 Subject: [PATCH] Update Versions --- .changepacks/changepack_log_release_staleness.json | 7 ------- Cargo.toml | 2 +- 2 files changed, 1 insertion(+), 8 deletions(-) delete mode 100644 .changepacks/changepack_log_release_staleness.json diff --git a/.changepacks/changepack_log_release_staleness.json b/.changepacks/changepack_log_release_staleness.json deleted file mode 100644 index b091cd3..0000000 --- a/.changepacks/changepack_log_release_staleness.json +++ /dev/null @@ -1,7 +0,0 @@ -{ - "changes": { - "crates/devup-mcp/Cargo.toml": "Patch" - }, - "note": "Stop a superseded run from deciding the release. The changepacks job runs after verify, which takes about ten minutes, so by the time it evaluates, main may already be several commits further on and it judges a state that no longer exists. On 2026-09-08 three merges landed inside one such window: each stale run opened a fresh Update Versions pull request instead of releasing, all three were merged, and the workspace went 0.2.1 to 0.3.0 to 0.3.1 while the newest release stayed 0.2.1. Nothing was tagged, and re-running could not recover it, because the action only cuts a release in the run that actually consumes the changepacks and by then there were none left - a version that moved without releasing cannot be un-moved. The job now compares its own commit with the tip of main and stands down when it has been replaced, leaving the decision to the run for the commit that replaced it.", - "date": "2026-09-08T20:30:00+09:00" -} diff --git a/Cargo.toml b/Cargo.toml index 947808e..5b9dc67 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -8,7 +8,7 @@ members = [ resolver = "3" [workspace.package] -version = "0.3.1" +version = "0.3.2" edition = "2024" rust-version = "1.98" license = "MIT"