chore: bump pins — portfolio v0.16.0, project_board v0.29.3 — re-verify against core 0.93.1#28
Conversation
|
👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow. |
![protoquinn[bot]](https://avatars.githubusercontent.com/in/3282126?s=60&v=4){kind=small}
There was a problem hiding this comment.
QA Audit — PR #28 | chore: bump pins — portfolio v0.16.0, project_board v0.29.3 — re-verify against core 0.93.1
VERDICT: WARN
CI Status
- No CI checks found for head d79b2ba — CI not accessible to reviewer (Gap)
Diff Review
- Single-file bump in
protoagent.bundle.yaml:verified_against0.81.0→0.93.1,portfoliov0.14.7→v0.16.0,project_boardv0.25.0→v0.29.3 - All bumps are forward; no downgrades or reordering
- Rationale in PR body for the board v0.29.3 pin is clear: force-disables
manage_giton scoped coder dispatch (projectBoard-plugin#69), preventing duplicate branches/PRs on provisioned teams
Observations
- GAP: Cannot verify tags
v0.16.0(portfolio-plugin) andv0.29.3(projectBoard-plugin) exist — tooling doesn't support cross-repo tag checks. Author should confirm both tags are pushed before merging. - GAP: No CI checks visible to reviewer — unable to confirm the verify workflow ran against core 0.93.1 as the
verified_againstbump implies.
No blocking defects found. The approve-on-green policy does not apply (no CI pipeline detected), so a human should confirm the tags exist and merge manually.
— Quinn, QA Engineer
|
Submitted COMMENT review on #28. |
v0.29.3 force-disables manage_git on the board's scoped coder dispatch (projectBoard-plugin#69) — on ≤v0.29.2 a manage_git:true team coder gets a second full git lifecycle from the adapter and every feature ships duplicate branches/PRs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mabry1985
force-pushed
the
chore/board-0.29.3
branch
from
d79b2ba to
dc2edd9
Compare
|
✅ CI went terminal-green with no blockers on the prior review — promoting it to APPROVED per the approve-on-green policy (#748). |
There was a problem hiding this comment.
QA Audit — PR #28 | chore: bump pins — portfolio v0.16.0, project_board v0.29.3 — re-verify against core 0.93.1
VERDICT: WARN
CI Status
- bump: skipped
- verify: queued ⏳
CI is still settling. The approve-on-green policy will promote this review to APPROVED automatically once every check passes — no manual re-review needed when CI goes terminal-green.
Diff Review (incremental: d79b2ba → dc2edd9)
- Single-line forward bump:
project_boardv0.29.2 → v0.29.3 - Rationale in PR body is clear: force-disables
manage_giton scoped coder dispatch (projectBoard-plugin#69), preventing duplicate branches/PRs on provisioned teams - All prior bumps (portfolio v0.16.0, verified_against 0.93.1) carried forward unchanged
Observations
- GAP: Cannot verify tag
v0.29.3exists onprotoLabsAI/projectBoard-plugin— tooling doesn't support cross-repo tag checks. Author should confirm before merge. - GAP: CI
verifycheck is queued — unable to confirm the verify workflow passes against core 0.93.1 until it completes. The approve-on-green policy handles this automatically once it settles.
No blocking defects. The one-line change is forward-only and well-motivated.
— Quinn, QA Engineer
|
Submitted COMMENT review on |
1 participant
Carries yesterday's unfinished pins branch (
chore/bump-pins-verify-0.93.1, cherry-picked) plus one more notch on the board pin.Why v0.29.3 specifically (delivery-loop plan M0 / M7 "patch early"): it force-disables
manage_giton the board's scoped coder dispatch (projectBoard-plugin#69). The teams this stack provisions runmanage_git: truecoders from the team template — on ≤v0.29.2 the board's dispatch double-runs the git lifecycle and every board-built feature gets duplicate branches/PRs.Companion: protoLabsAI/leadEngineer#5.
🤖 Generated with Claude Code