Skip to content

chore(release): v1.2.0 - #52

Merged
crisng95 merged 1 commit into
mainfrom
chore/release-v1.2.0
Sep 17, 2026
Merged

crisng95 merged 1 commit into
mainfrom
chore/release-v1.2.0

Conversation

@crisng95

Copy link
Copy Markdown
Owner

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.pyFastAPI(version=…) 1.1.01.2.0. This is the canonical version; 939b956 established that a release touches exactly this line.
  • README.md — the changelog's ### Unreleased heading becomes ### v1.2.0 — 2026-09-18.

The drift this also fixes

ccf89c6 put "0.2.0" in two places in agent/main.py. The v1.1.0 release bumped only the FastAPI(...) line, so /health has been answering 0.2.0 ever since while the app reported 1.1.0 — three releases stale, on the endpoint CLAUDE.md tells you to curl before doing anything else:

curl -s http://127.0.0.1:8100/health

Releasing again would have widened the gap to four. /health now reads app.version instead 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.json stays at 0.3.2. It tracks the extension's own lifecycle, and a bump there forces a user-visible reload in chrome://extensions. dashboard/package.json stays at 0.0.0 — never released.

Verification

  • pytest tests/unit272 passed (with ffmpeg-full ahead on PATH; a stock Homebrew ffmpeg lacks drawtext and fails 13 unrelated tests)
  • /health and app.version both return 1.2.0, checked by calling the handler rather than reading the source — TestClient cannot be used here, the lifespan installs signal handlers and only runs on the main thread

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 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:

git checkout main && git pull
git tag -a v1.2.0 -m "v1.2.0"
git push origin v1.2.0
gh release create v1.2.0 --title "v1.2.0" --notes-from-tag

🤖 Generated with Claude Code

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
crisng95 force-pushed the chore/release-v1.2.0 branch from aa2018a to 5cc9dbd Compare September 17, 2026 17:33
@crisng95
crisng95 merged commit 57b52e6 into main Sep 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant