chore: bump pins (portfolio v0.16.0, project_board v0.29.2) + re-verify vs core 0.93.1#27
Merged
Merged
Conversation
…fy against core 0.93.1 portfolio v0.14.7 -> v0.16.0, project_board v0.25.0 -> v0.29.2 (both flagged by scripts/check_bundle_updates.py). Bump verified_against 0.81.0 -> 0.93.1 so the verify workflow smokes this pin set against current protoAgent core. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
👀 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 #27 | chore: bump pins (portfolio v0.16.0, project_board v0.29.2) + re-verify vs core 0.93.1
VERDICT: PASS (pending CI settle)
CI Status
- bump: skipped
- verify: queued
Diff Review
- 1 file, 6 lines changed —
protoagent.bundle.yamlonly portfoliov0.14.7 → v0.16.0,project_boardv0.25.0 → v0.29.2,verified_against0.81.0 → 0.93.1- All changes are version-string bumps; no logic, schema, or plugin-ordering changes
githubandagent_browserpins left untouched — consistent with PR description stating they're already current
Observations
- None. The diff is a clean config update matching what
check_bundle_updates.pyflagged.
⏳ CI is still settling. Per the approve-on-green policy, this COMMENTED review promotes to a formal APPROVED automatically once every check completes terminal-green — no manual re-review needed.
— Quinn, QA Engineer
|
Submitted COMMENT review on #27. |
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.
The bundle's own
check_bundle_updates.pyflagged two stale pins;verified_againstwas also 12 minors behind core.portfoliov0.14.7 → v0.16.0 (PM-side task cancel + dispatch dedup + dashboard fixes)project_boardv0.25.0 → v0.29.2verified_against0.81.0 → 0.93.1 — so verify-bundle.yml smokes this set against current coregithubv0.1.3 andagent_browserv0.5.1 already currentContext: standing up roxy as this bundle's reference-host PM (homelab fleet); wanted the pin set current + re-verified before deploy.
🤖 Generated with Claude Code