Repository navigation
feat(site): describe 0.2.3 and the compatibility record - #3
Merged
Merged
Conversation
…renook's replays check /compatibility opens on a wall of blocks, one for each answer recorded from the official emulator or from production Firebase, a row per service: lit where a replay checks Firenook gives the same answer, outlined where it answers differently on purpose, grey where the replay is still to come; flame for production, amber for the official emulator. Pointing at a block shows the request, the recorded answer, what the replay compares and where it was recorded; the buttons light one reference's answers. Under it, the record release by release, each service's recorded sets, where Firenook takes a side between the official emulator and production, and every difference found and fixed. scripts/conformance/import.mjs builds the data from a release's conformance-cases.json and conformance-verify.json; each block's detail is fetched only when someone points at it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GojiTpvSY8YywZFwh2ZJg2
The docs move to 0.2.3 and engine 2294132: the Firestore page's queries and indexes (warnings, --strict-indexes, the watched file, the Indexes page and firestore_missing_indexes), the CLI reference's --strict-indexes, the release container image on the Docker page, 55 MCP tools from the candidate's own tools/list, and the coverage lists. The Auth events caution and its known issue go: since 0.2.2 nothing is sent to the Functions port without Functions. Data moves between 0.2.3 and 0.2.0 as it is. The changelog, the publish date and the compatibility record follow once 0.2.3 is on npm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GojiTpvSY8YywZFwh2ZJg2
…4132 (a preview until the 0.2.3 release's own files) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GojiTpvSY8YywZFwh2ZJg2
The changelog copied from packaging/CHANGELOG.md at npm-v0.2.3 (0.2.2 and 0.2.3 added, the one benchmarks link made relative to the site), with both releases' npm dates. The compatibility record is imported from the 0.2.3 release's own conformance-cases.json and conformance-verify.json, and is the same as the preview from main's CI: 6,592 answers recorded, 5,874 checked, 202 different on purpose. The three issues fixed for the next release are listed under 0.2.3, so the page says every difference found is fixed. Data moves between 0.2.3, 0.2.2, 0.2.1 and 0.2.0 as it is. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GojiTpvSY8YywZFwh2ZJg2
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.
Brings the site up to Firenook 0.2.3, published on 2026-11-12, and adds the compatibility record (firenook-dev/firenook#156). Merging this deploys it to firenook.dev.
Changed
conformance-cases.jsonandconformance-verify.json: 6,592 answers recorded, 5,874 replayed and the same, 202 different on purpose, 516 not replayed yet.2294132in sample output, install and verification commands. Firestore's queries and indexes (the Indexes page, the missing-index warnings,--strict-indexes), the release container image on the Docker page,--strict-indexesin the CLI reference, the 55 MCP tools, and data moving between 0.2.3, 0.2.2, 0.2.1 and 0.2.0 as it is.Checked locally:
astro check0 errors, 91 pages built,check:sitefound no problems across 9,152 internal links. /compatibility was looked at on desktop and at 390 px, with every block's card inside the page and no sideways scroll.🤖 Generated with Claude Code
https://claude.ai/code/session_01GojiTpvSY8YywZFwh2ZJg2