Repository navigation
feat(site): 0.2.5 as published - #7
Merged
Merged
Conversation
The changelog copied from packaging/CHANGELOG.md at npm-v0.2.5 (the one benchmarks link made relative to the site), with its npm date. The record imported from the release's own conformance-cases.json and conformance-verify.json: 6,791 answers in 43 sets, 6,439 compared exactly, 351 different on purpose, 1 not replayed (#247); the record link points at COMPATIBILITY.md at npm-v0.2.5 and the release-by-release chart gains 0.2.5. The docs move to 0.2.5 and engine 6683b3e: versions, the CLI reference, install, CI, tests, Docker's image tags and the samples. Data moves between 0.2.5 and 0.2.0 as it is. The MCP list is 0.2.5's tools/list, unchanged at 55. What 0.2.5 changed, from its own output: - Rules that compile with the official compiler's warnings print them at start-up and on each reload, such as "firestore.rules:5:19 - WARNING Invalid method name: writes." (#229). - A transaction's queries are checked at commit, including one that found nothing (#235), on the Firestore page and the compatibility list. - A token the Admin SDK sets in firebaseStorageDownloadTokens becomes the file's download token (#221), on the Storage page and the compatibility list. #235 and #221 join the differences people found, under 0.2.5. 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.
The changelog copied from packaging/CHANGELOG.md at npm-v0.2.5 (the one
benchmarks link made relative to the site), with its npm date. The record
imported from the release's own conformance-cases.json and
conformance-verify.json: 6,791 answers in 43 sets, 6,439 compared exactly,
351 different on purpose, 1 not replayed (#247); the record link points at
COMPATIBILITY.md at npm-v0.2.5 and the release-by-release chart gains 0.2.5.
The docs move to 0.2.5 and engine 6683b3e: versions, the CLI reference,
install, CI, tests, Docker's image tags and the samples. Data moves between
0.2.5 and 0.2.0 as it is. The MCP list is 0.2.5's tools/list, unchanged at
55.
What 0.2.5 changed, from its own output:
start-up and on each reload, such as "firestore.rules:5:19 - WARNING
Invalid method name: writes." (#229).
nothing (#235), on the Firestore page and the compatibility list.
file's download token (#221), on the Storage page and the compatibility
list.
#235 and #221 join the differences people found, under 0.2.5.
Checked locally:
npm run build(93 pages),npm run check(0 errors),npm run check:site(9,304 internal links, no problems).🤖 Generated with Claude Code
https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g