Skip to content

chore(release): prepare 0.2.3 (engine 2294132, the Indexes page, three reported bugs fixed, a container image) - #184

Merged
sanjevirau merged 1 commit into
mainfrom
release/0.2.3
Nov 12, 2026
Merged

sanjevirau merged 1 commit into
mainfrom
release/0.2.3

Conversation

@sanjevirau

Copy link
Copy Markdown
Collaborator

Prepares 0.2.3: the CLI, its five native packages and both server.json versions go to 0.2.3, the engine is pinned to 2294132253f03395b0d9bafe391d35075e928112 (main after every 0.2.3 pull request merged, the merge of #182), and the changelog says what changed since 0.2.2 and who it came from.

No package or image is published from this PR. Tagging npm-v0.2.3, dispatching Reviewed npm release with latest and approving npm-release stay with the release owner; the container image publishes in that same approved run, after npm.

In 0.2.3

Checks on the exact engine commit

Check Result
CI (run 43084842804) 22 of 22 jobs
Packed install, five platforms (run 43084869443) all five passed, and the packed artifacts verified
Real SDK clients (run 43084875694) web, iOS and Android passed
The reporters' flows through npx firenook, against firebase-tools 15.34.0 #174 identical; #175 every step the same (23 of 23 lines, as JSON values); #169: in all four cases (GET and batchGet, missing and present document) one commit wins and the other is ABORTED, where 0.2.2 let both GET commits of a missing document through (firebase-tools aborts both: it locks)
Data, a real 35 GB store (2,748,678 documents, 35,914 files) 0.2.2 reads it, 0.2.3 reads it, changes it, 0.2.2 reads the result, 0.2.3 reads it again: every phase stops cleanly, with no repair or rebuild, and the fingerprints are equal except where #174 means them to differ: the Cloud Storage API now lists the download tokens 2,778 files already held (50 sampled, every one equal to the token 0.2.2 reports)
The console's full journey suite through npx firenook 374 passed, 10 skipped, 3 failed: shell-engines.spec.ts:245, which fails the same way on 0.2.2, and two Logs journeys that then passed 10 of 10 alone and in the whole observe group (39 of 39)
The contributed rules cases (#183) 29 of 29 verdicts and status codes on the official emulator 1.22.0 (the recorded jar) and on this engine
node --test packaging/*.test.mjs, check-release.mjs 192 of 192; release contract firenook@0.2.3

Not run for this patch: the speed bench (#176 measured its own per-query cost against main; the other fixes are off the query path), the paired acceptance run and a real application in a browser.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GojiTpvSY8YywZFwh2ZJg2

…e reported bugs fixed, a container image)

The CLI and its five native packages go to 0.2.3, the MCP Registry entry
names it, the engine is pinned to main after every 0.2.3 pull request
merged, and the changelog says what changed since 0.2.2 and who it came
from.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GojiTpvSY8YywZFwh2ZJg2
@sanjevirau
sanjevirau merged commit 04a7b98 into main Nov 12, 2026
53 of 58 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