chore: prepare release 0.7.5

[steipete]

Summary

• date the 0.7.5 changelog section for release
• update pinned Linux package examples to 0.7.5

Verification

• go test ./...
• make build
• goreleaser release --snapshot --clean

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed July 4, 2026, 12:21 PM ET / 16:21 UTC.

Summary
The PR dates the 0.7.5 changelog entry and updates the README Linux package examples from 0.7.4 to 0.7.5.

Reproducibility: not applicable. this is a release administration PR rather than a runtime bug. The relevant check is source and release-state inspection: the branch changes docs to 0.7.5, while v0.7.5 is not yet published.

Review metrics: 1 noteworthy metric.

• Release text scope: 2 files changed, 4 additions and 4 deletions. The diff is limited to release-facing documentation, so review should focus on version accuracy and release timing.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🌊 off-meta tidepool
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• Merge only when v0.7.5 tag and release asset publication are ready.

Risk before merge

• [P1] README package commands will reference v0.7.5 assets before the v0.7.5 release exists, so this should merge only during the release publication window.

Maintainer options:

1. Merge with release publication (recommended)
   Merge this when the v0.7.5 tag and release assets are ready so the README install commands do not point at missing downloads.
2. Pause until the release window
   If v0.7.5 is not being published now, leave the PR open until the release can be cut with the docs update.

Next step before merge

• A release owner should merge this when they are ready to tag and publish v0.7.5; there is no automated repair to queue.

Security
Cleared: The diff only updates release-facing text and does not change code execution, dependencies, workflows, secrets, or package sources.

Review details

Best possible solution:

Land the changelog date and README version bump as part of v0.7.5 publication so the examples stay aligned with published GitHub Release assets.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is a release administration PR rather than a runtime bug. The relevant check is source and release-state inspection: the branch changes docs to 0.7.5, while v0.7.5 is not yet published.

Is this the best way to solve the issue?

Yes, if it is release-coupled. The patch follows the previous release-prep pattern and preserves the package URL templates; the safer alternative is to wait to merge until v0.7.5 publication is imminent.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning high; reviewed against 1d54439c3e18.

Label changes

Label changes:

• add P3: This is a low-risk release administration/docs PR with a narrow diff.
• add merge-risk: 🚨 other: The README install examples will point to v0.7.5 downloads that do not exist until the release is published.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.

Label justifications:

• P3: This is a low-risk release administration/docs PR with a narrow diff.
• merge-risk: 🚨 other: The README install examples will point to v0.7.5 downloads that do not exist until the release is published.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.

Evidence reviewed

What I checked:

• Repository policy check: No AGENTS.md was found under the target repository root, so no target-specific AGENTS.md policy applied. (1d54439c3e18)
• PR diff scope: The branch changes only CHANGELOG.md and README.md, with 4 additions and 4 deletions for the release date and package example version bump. (272e96998cfd)
• Changed changelog entry: At PR head, the 0.7.5 changelog heading is dated 2026-07-04 while retaining the existing performance note from current main. (CHANGELOG.md:3, 272e96998cfd)
• Changed README examples: At PR head, the Linux package examples set version=0.7.5 while preserving the existing GitHub Releases URL templates. (README.md:90, 272e96998cfd)
• Package naming check: The v0.7.4 GitHub release has matching .deb and .rpm asset names for the README templates, so the 0.7.5 text follows the current published pattern. (README.md:96, f360e9cc6fb7)
• Release availability check: gh reported that v0.7.5 is not found, so the README version bump should be merged only as part of the v0.7.5 publication flow.

Likely related people:

• steipete: Git blame and file history show recent changes to the changelog release section, README package examples, and GoReleaser package naming on the current main history. (role: recent release-doc contributor; confidence: high; commits: f360e9cc6fb7, 551b557e9e75, 1d54439c3e18; files: CHANGELOG.md, README.md, .goreleaser.yml)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.