chore(release): v1.2.0 - #52
Merged
Merged
Conversation
First release since v1.1.0 (2026-05-09), and it is one arc: Flow moved to flow.google.com in September 2026 and stopped minting the bearer the old REST API needed, so the transport was rebuilt on batchexecute (#39), the dead REST path deleted (#49), the image API migrated (#42), and the Omni image-conditioned modes ported back on top of it (#48/#50). Also fixes a version drift this release would otherwise have deepened. ccf89c6 put "0.2.0" in two places in agent/main.py; 939b956 bumped only the FastAPI line, so /health has reported 0.2.0 ever since while the app said 1.1.0 — three releases stale, on the endpoint CLAUDE.md tells you to curl before anything else. /health now reads app.version, so there is one string to bump instead of two literals that agree only by luck. extension/manifest.json is deliberately not bumped. It tracks the extension's own lifecycle, it is at 0.3.2, and a bump there forces a user-visible reload. Verified: 272 passed; /health and app.version both report 1.2.0, checked by calling the handler rather than reading the source. Not verified: the Omni envelopes from #48. They are live-verified per that PR and the tests lock their shape, but nothing has submitted through a signed-in Flow tab since the merge resolution. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E5BJVhNgerhFTUgmfnKTSj
crisng95
force-pushed
the
chore/release-v1.2.0
branch
from
September 17, 2026 17:33
aa2018a to
5cc9dbd
Compare
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
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.
Release commit for v1.2.0 — the first since
v1.1.0(2026-05-09).What's in it
One line of substance plus one bug fix:
agent/main.py—FastAPI(version=…)1.1.0→1.2.0. This is the canonical version;939b956established that a release touches exactly this line.README.md— the changelog's### Unreleasedheading becomes### v1.2.0 — 2026-09-18.The drift this also fixes
ccf89c6put"0.2.0"in two places inagent/main.py. The v1.1.0 release bumped only theFastAPI(...)line, so/healthhas been answering0.2.0ever since while the app reported1.1.0— three releases stale, on the endpointCLAUDE.mdtells you to curl before doing anything else:Releasing again would have widened the gap to four.
/healthnow readsapp.versioninstead of restating it, so there is one string to bump rather than two literals that agree only by luck.What is deliberately not bumped
extension/manifest.jsonstays at0.3.2. It tracks the extension's own lifecycle, and a bump there forces a user-visible reload inchrome://extensions.dashboard/package.jsonstays at0.0.0— never released.Verification
pytest tests/unit→ 272 passed (withffmpeg-fullahead onPATH; a stock Homebrewffmpeglacksdrawtextand fails 13 unrelated tests)/healthandapp.versionboth return1.2.0, checked by calling the handler rather than reading the source —TestClientcannot be used here, the lifespan installs signal handlers and only runs on the main threadNot verified
The Omni envelopes from #48. They are live-verified per that PR and the tests lock their shape, but nothing has submitted through a signed-in Flow tab since the merge resolution in #50. Worth one real Omni first-frame generation before cutting the tag if you want the release to stand on more than unit tests.
After merge
No CI exists, so the tag is the record rather than a trigger, and nothing publishes:
🤖 Generated with Claude Code