chore: release v0.7.1 - #30
Merged
Merged
Conversation
- Contents reads are GETs (#29): `github_read_file`, `github_read_pr_file`, `github_path_exists` and `github_repo_contents` passed the ref as `-f ref=`, which made `gh api` send POST, and GitHub 404s a POST to /contents. Every ref-pinned read failed; the QA panel's lanes reviewed diffs blind (pr-reviewer-plugin#118). - Adds the standard release caller (`.github/workflows/release.yml`, the reusable release-tools plugin-release workflow) so this plugin releases like the others. - uv.lock's own version entry had drifted to 0.5.0; now 0.7.1. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LSRkzcPyaDrKSY7geFuGr3
![protoreview[bot]](https://avatars.githubusercontent.com/in/4233969?s=60&v=4){kind=small}
There was a problem hiding this comment.
QA panel review — PASS
code-review-structural · head 2f4a64707531 · formal
All four LLM finders returned clean; the structural verification pass confirmed an empty array with nothing to verify. Overall risk is low. No fix-first item, no panel disagreements, and no prior blockers to disposition. One residual gap: the cross-repo reference to protoLabsAI/release-tools/.github/workflows/plugin-release.yml@v2 cannot be verified from this repository and remains an open question for the author. The structural pass was a no-op (no findings to verify), so structural coverage is effectively absent for this PR.
No findings — the review came back clean.
findings JSON (machine-readable)
[]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases github-plugin v0.7.1, the version the QA reviewer's image will pin.
-f ref=made gh send POST, a 404 #29). The four read tools passed the ref as-f ref=. That madegh apisend a POST, and GitHub answers a POST to/contentswith 404. Every ref-pinned read failed, so the QA panel's lanes reviewed diffs blind (Repository file reads return 404 during panel review, forcing lanes to review diffs blind pr-reviewer-plugin#118)..github/workflows/release.ymldelegates to release-tools' reusableplugin-release.yml, the same thin caller pr-reviewer-plugin uses. This repo had none, so v0.5.0 to v0.7.0 were cut by hand. Merging this PR with the subjectchore: release v0.7.1fires it: the tag, the GitHub release with notes, and the Discord notice.uv.lock's own version entry was stale at 0.5.0. Relocking changed only that line.Tests pass, 278 of 278.
ruff checkandruff format --checkare clean (0.15.10).🤖 Generated with Claude Code
https://claude.ai/code/session_01LSRkzcPyaDrKSY7geFuGr3