Release v0.4.1 (#61)

Fixes a release-pipeline test bug that prevented v0.4.0's artifacts from
publishing: integration-update.sh Test 4 ("dev build refusal") relied on
git state to produce a dev binary, which fails when CI runs on a commit
tagged v{cargo_version}. Test 4 now sets COOP_FORCE_BUILD_KIND=dev
explicitly, mirroring Test 1's =release override.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hbrodin

CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## v0.4.1
+
+Re-release of v0.4.0. The v0.4.0 tag did not produce release artifacts
+because `tests/integration-update.sh` Test 4 ("dev build refusal") fails
+whenever CI runs on a commit tagged `v{cargo_version}` — `build.rs`
+correctly bakes `COOP_BUILD_KIND=release` for that commit, so the test's
+unset-override path produced a release binary instead of a dev one. Test 4
+now sets `COOP_FORCE_BUILD_KIND=dev` explicitly, mirroring Test 1's
+`=release` override. No functional changes to `coop` itself since v0.4.0.
+
 ## v0.4.0
 
 ### New features

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "coop"
-version = "0.4.0"
+version = "0.4.1"
 edition = "2024"
 description = "Isolated VM environment for running Claude Code"
 

Cargo.toml

@@ -19,8 +19,9 @@ fn main() {
     for path in git_rerun_paths() {
         println!("cargo:rerun-if-changed={}", path.display());
     }
-    // Build-time test hook: allows the integration test to produce a "release" binary from
-    // an untagged branch. Runtime behaviour is unaffected — the override only influences
+    // Build-time test hook: lets the integration test pin `COOP_BUILD_KIND` to either
+    // "release" (from an untagged branch) or "dev" (from a tagged commit), independent
+    // of git state. Runtime behaviour is unaffected — the override only influences
     // what build.rs bakes into `COOP_BUILD_KIND`.
     println!("cargo:rerun-if-env-changed=COOP_FORCE_BUILD_KIND");
 

build.rs

@@ -221,10 +221,12 @@ fi
 # ── Test 4: dev build refuses to self-update ─────────────────────────────────
 
 echo "==> Building dev binary..."
+# Force kind=dev rather than relying on git state. When CI runs on a tag
+# matching the Cargo version (the release workflow's normal trigger),
+# build.rs correctly bakes kind=release, which would defeat this test.
 (
     cd "$PROJECT_DIR"
-    unset COOP_FORCE_BUILD_KIND
-    cargo build --release --quiet
+    COOP_FORCE_BUILD_KIND=dev cargo build --release --quiet
 )
 cp "$PROJECT_DIR/target/release/coop" "$TMPDIR/bin/coop-dev"