Repository navigation
feat(site): 0.2.4 as published - #4
Merged
Merged
Conversation
Imported from the npm-v0.2.4 release's own conformance-cases.json and conformance-verify.json: 6,791 answers recorded in 43 sets, 1,681 of them from production; 6,414 compared exactly, 351 different on purpose and 26 not replayed (#229, all Firestore rules reloads). The record link points at COMPATIBILITY.md at npm-v0.2.4, and the release-by-release chart gains 0.2.3 (6,592) and 0.2.4 (6,791), so the page counts to the release it shows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g
The changelog copied from packaging/CHANGELOG.md at npm-v0.2.4 (the one benchmarks link made relative to the site), with its npm date. The docs move to 0.2.4 and engine 4be26be: versions, the CLI reference, install, CI, tests, Docker's image tags, the samples, and Rust 1.100.0 for the build. Data moves between 0.2.4 and 0.2.0 as it is. The MCP list is 0.2.4's tools/list, unchanged at 55. What 0.2.4 changed, from its own output: - --keep-data: init writes, prints and runs it only with Firestore, Auth and Storage; the launcher refuses it before the engine starts otherwise, naming what is missing and where to add it (#187). - A Functions save that does not load prints the official "Failed to load function definition from source" line in plain output and the debug log (#188). - functions:invoke sends a scheduled function its schedule event without --event-data, and refuses --data and --method for it (#189). - The logging listener runs whether or not the UI does, and moves to the next free port when 4500 is taken and nothing chose it (#210). - Rules that do not compile are reported in the official parser's words, and the HTTP reload answers "Error compiling rules:" (#207). The three known issues #187, #188 and #189 go: 0.2.4 fixes them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g
"The first release for public use" took the newest stable release instead of the oldest, and the benchmark note named the latest release, though the record it links is 0.2.0's. Both read 0.2.4 once the site moved to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g
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.
firenook.dev for Firenook 0.2.4, published 2026-11-13. A patch release, so the recordings stay; the version, changelog, docs samples and compatibility record move.
conformance-cases.jsonandconformance-verify.json. It shows 6,791 answers recorded and 6,765 replayed: 6,414 compared exactly, 351 different on purpose. The other 26 are Firestore rules compile errors, listed under Rules reload: 26 compile errors still answered otherwise than the official emulator firenook#229. The history chart gains 0.2.3 and 0.2.4. The known issues #187, #188 and #189 leave the page, since 0.2.4 fixes them.npm-v0.2.4, and its publication time. The page names 0.2.0 where it means the first public release, so that line no longer moves with each version.functions:invokesends a scheduled function its event (#189);--keep-data's refusal andfirenook init's script (#187);Checks:
astro check(0 errors), the build (every link valid),check:site,package, andcf deploy --prebuilt --dry-run.🤖 Generated with Claude Code
https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g