Skip to content

chore: bump plugin pins to latest release tags - #9

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
bump-pins
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
bump-pins

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Automated pin bump (ADR 0049).

bump: terminal v0.9.5 -> v0.10.0  [OUT OF RANGE — review before merging]
bump: github v0.9.3 -> v0.12.1  [OUT OF RANGE — review before merging]

Merging requires the verify job green — the pin only moves through a passing verification.

This PR was opened with the repository GITHUB_TOKEN, so GitHub holds its verify run for approval (Actions tab -> Approve and run workflows) instead of starting it automatically — the documented explicit-approval contract, see README.md's "Pin-bump PR lifecycle" section (#2645). A later scheduled run updates THIS PR in place rather than opening a new one.

@github-actions github-actions Bot added the needs-approval A workflow run is stuck action_required and needs a maintainer to approve it label Oct 26, 2026
@github-actions

Copy link
Copy Markdown
Author

Pin-bump PR #9 needs a maintainer to approve its verify run — its verify run concluded action_required with no jobs started. GITHUB_TOKEN-authored PRs don't run pull_request workflows automatically; click Approve and run workflows on the Actions tab (https://github.com/protoLabsAI/engineer-archetype/actions/runs/40282791035). This is the documented explicit-approval step (README.md "Pin-bump PR lifecycle", #2645) — approve it (or close the PR) so the pin doesn't sit unverified.

@protoreview protoreview Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA panel review — PASS

code-review · head 39d74799c05d · formal

PR #9 is clean: all four review angles (correctness, cross-file, security, style) returned no findings, and the verifier confirmed there was nothing to verify. No defects, no disagreements, no coverage gaps. Nothing to fix.

No findings — the review came back clean.

findings JSON (machine-readable)
[]

@protoreview protoreview Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA panel review — PASS

code-review · head cbe3571cfd44 · formal

Single-line pin bump; all four finders independently found no defects. No panel disagreement, no coverage gaps. Verification confirmed the clean result — nothing to verify, nothing to drop. No action required.

No findings — the review came back clean.

findings JSON (machine-readable)
[]

@protoreview protoreview Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA panel review — PASS

code-review · head 514bb4079bb2 · formal

PR #9 is clean: the panel produced no findings and the verifier confirmed there was nothing to verify. No disagreements, no coverage gaps to flag. Nothing to fix before merge.

No findings — the review came back clean.

findings JSON (machine-readable)
[]

@protoreview protoreview Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA panel review — PASS

code-review · head aa3f9805accc · formal

Low-risk PR: a version bump in the bundle plus a README that wasn't updated to match. The one thing to fix is the stale pin version in the README (line 72 says v0.9.0, should say v0.10.0). The panel was unanimous — a single finding, confirmed by the verifier. No coverage gaps; the diff is small and fully covered.

Findings

Severity Location Finding Verified
🟡 minor README.md:72 README states 'the bundle pins v0.9.0' but the PR changes the bundle to pin v0.10.0, making the docs factually wrong about the current pin. confirmed
findings JSON (machine-readable)
[
  {
    "file": "README.md",
    "line": 72,
    "severity": "minor",
    "category": "conventions",
    "claim": "README states 'the bundle pins v0.9.0' but the PR changes the bundle to pin v0.10.0, making the docs factually wrong about the current pin.",
    "evidence": "so it also works on a fleet member behind the hub (terminal-plugin v0.5.1+; the bundle pins v0.9.0). On Windows it needs",
    "verdict": "confirmed",
    "note": "Diff bumps terminal ref to v0.10.0; README line 72 at PR head still says 'the bundle pins v0.9.0'."
  }
]

1 finding(s) excluded from the verdict by in-diff confinement (file not among this PR's changed paths):

  • README.md (minor) — README states 'the bundle pins v0.9.0' but the PR changes the bundle to pin v0.10.0, making the docs factually wrong about the current pin.

Runner context: observed. Native parent-conversation exclusion and separate history exclusion are checked per execution. Intended prior findings may remain in the rendered prompt. Instruction-source observations describe the assembled system prompt; mandatory repository guidance remains applicable. External instruction sources and runtime additions remain unknown. Tool observations describe bound tools, inherited fence and enforcement; external policy remains unknown. Construction evidence does not establish semantic review coverage.

Raw finding accounting: unsupported
{"supported": false, "complete": null, "gaps": [], "status": "unsupported"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-approval A workflow run is stuck action_required and needs a maintainer to approve it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant