chore: release v0.0.42

[polaz]

Why

release-plz is deadlocked. Its Create release PR job runs cargo package over the workspace at the last-release baseline (v0.0.41), and the v0.0.41 tree has ffi-bench depending on structured-zstd by path only (no version). cargo rejects that when packaging:

error: failed to verify manifest at ffi-bench/Cargo.toml
  all dependencies must have a version requirement specified when packaging.
  dependency `structured-zstd` does not specify a version

PR #435 fixed this on main, but the v0.0.41 tag tree is immutable — release-plz keeps packaging the broken baseline, so every run since the v0.0.41 release (#432, #433, #435) is red. No main commit can change what release-plz packages for the v0.0.41 baseline.

Fix

Bump structured-zstd 0.0.41 → 0.0.42 and cut v0.0.42 manually, moving release-plz's baseline past the broken v0.0.41 tree. The v0.0.42 tree already carries the #435 ffi-bench version fix, so cargo package --workspace passes against it (verified locally: full cargo package --workspace is green on current main).

Required follow-up (manual, after merge)

release-plz cannot create the release itself while deadlocked. After this merges, create the GitHub release so the tag lands and release.yml (trigger: release: created) runs:

gh release create v0.0.42 --target main --title "v0.0.42" --generate-notes

Once tag v0.0.42 exists, release-plz's next run packages the v0.0.42 baseline (with the fix) and works again. CHANGELOG is left to release-plz (manual edits are guarded / overwritten by its next run).

Summary by CodeRabbit

• Chores
  • Bumped package version to 0.0.42.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 12cb766d-af63-470b-b455-6490e7b63f8d

📥 Commits

Reviewing files that changed from the base of the PR and between e4c4bef and f22dc56.

📒 Files selected for processing (1)

• zstd/Cargo.toml

---

📝 Walkthrough

Walkthrough

The version field in zstd/Cargo.toml is incremented from 0.0.41 to 0.0.42. No other files, dependencies, features, or manifest fields are modified.

Changes

zstd Crate Version Bump

Layer / File(s)	Summary
Package version increment zstd/Cargo.toml	version field updated from 0.0.41 to 0.0.42.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Possibly related PRs

• structured-world/structured-zstd#374: Identical change type — a sole zstd/Cargo.toml crate version bump, representing a prior release-manifest increment.

Poem

🐇 A tiny hop, a digit flips,
From forty-one to forty-two it skips.
No grand refactor, no sweeping change—
Just one small bump across the range.
The rabbit stamps the manifest with cheer! 🎉

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-v0.0.42

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

• Bumps structured-zstd from 0.0.41 to 0.0.42 in zstd/Cargo.toml.
• Prepares the crate for the manual v0.0.42 release so release automation can move past the broken v0.0.41 baseline.

Confidence Score: 5/5

The change is merge-safe: it only updates the crate version for the release handoff.

The diff is limited to a manifest version bump that matches the stated release objective, with no code or dependency behavior changes.

T-Rex Logs

What T-Rex did

• T-Rex compared the base commit 0.0.41 with the head commit 0.0.42, observed the cargo: command not found environment blocker when running cargo package --workspace, and concluded that no contract-mismatch finding was filed because packaging did not reach Cargo manifest/package validation.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore: release v0.0.42" | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!