Repository navigation
chore(release): prepare 0.2.3 (engine 2294132, the Indexes page, three reported bugs fixed, a container image) - #184
Merged
Merged
Conversation
…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
This was referenced Nov 12, 2026
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.
Prepares 0.2.3: the CLI, its five native packages and both
server.jsonversions go to 0.2.3, the engine is pinned to2294132253f03395b0d9bafe391d35075e928112(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 withlatestand approvingnpm-releasestay with the release owner; the container image publishes in that same approved run, after npm.In 0.2.3
firestore.indexes.json, the index file watched like the rules file, andfirestore_missing_indexesover MCP (with fix(cli): accept --strict-indexes on emulators:start and emulators:exec #173,--strict-indexesthroughnpx firenook).PATCHof them (Auth emulator: project config route returns empty blockingFunctions although blocking functions are registered #175, reported by @10eputzen).ghcr.io/firenook-dev/firenook, built from the published npm version, tried, then pushed for linux/amd64 and linux/arm64 (Feature request: Provide OCI container image #145, asked for by @Chaz6).zip9.4.2, firebase-tools 15.35.0 and Playwright in the conformance tools,actions/setup-java6.2.0.Checks on the exact engine commit
npx firenook, against firebase-tools 15.34.0GETandbatchGet, missing and present document) one commit wins and the other is ABORTED, where 0.2.2 let bothGETcommits of a missing document through (firebase-tools aborts both: it locks)npx firenookshell-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 wholeobservegroup (39 of 39)node --test packaging/*.test.mjs,check-release.mjsfirenook@0.2.3Not 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