chore: release v0.16.0#60
Conversation
|
👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow. |
There was a problem hiding this comment.
QA Audit — PR #60 | chore: release v0.16.0
VERDICT: PASS (CI pending — non-blocking pass; formal approval queued once checks terminal)
CI Status
- Lint (ruff): queued
- Python tests: queued
- Web E2E smoke: queued
- Verify workspace config: queued
- A2A live smoke (lean tier): in_progress
Diff Review
Automated version bump: pyproject.toml 0.15.0 → 0.16.0 + CHANGELOG entry for eval-case requires_env gating. Clean, no code changes.
Observations
- LOW: CHANGELOG.md has two consecutive
[0.16.0] - 2026-06-06date headers (line 3–4). Likely a pre-existing double-header; not introduced by this PR but worth cleaning up before tag push so the release notes render cleanly. Trivial cosmetic fix.
Gaps
- CI not yet terminal; formal
APPROVEDwill be issued on next pass once checks complete.
— Quinn, QA Engineer
|
Submitted |
There was a problem hiding this comment.
QA Audit — PR #60 | chore: release v0.16.0
VERDICT: PASS (pending CI)
CI Status (all queued — awaiting terminal state)
- A2A live smoke (lean tier): queued
- Web E2E smoke: queued
- Verify workspace config: queued
- Lint (ruff): queued
- Python tests: queued
Diff Review
pyproject.toml: version0.15.0 → 0.16.0— standard semantic bump, correct.CHANGELOG.md: added comprehensive v0.16.0 changelog covering fleet toolkit, domain separation, operator-fork seam, board↔GitHub sync, and deploy guard — matches the PR description scope.- No code logic changes; purely a release-management diff.
Observations
- LOW: CI not yet terminal — formal PASS will follow once all checks complete.
- INFO: Release tag command per maintainer note:
git tag -a v0.16.0 -m 'Release v0.16.0' && git push origin v0.16.0. Do not also workflow_dispatchrelease.ymlafterward (redundant).
— Quinn, QA Engineer
|
CI is still running. Submitted a non-blocking Submitted COMMENT review on #60. |
Automated version bump to
v0.16.0. Review + merge through the normal CI/review gate, then push the tag to cut the release:git checkout main && git pull && git tag -a v0.16.0 -m 'Release v0.16.0' && git push origin v0.16.0. The tag push triggers release.yml (Docker tags + GitHub Release + Discord) — don't also workflow_dispatch release.yml afterward (redundant; 422s on the duplicate).