release(#23): cut the fix wave as v0.2 - #24
Merged
Merged
Conversation
The wave carries additive changes S11 assigns to a minor bump (unsupported_media_type) and subtractive MUSTs that make previously conforming servers non-conforming (sequential non-atomic execution, REQUIRED statementIndex, tagged-value emission) -- landing it labeled 0.1 made the document contradict its own wire version. One flip everywhere: SPEC self-references, wire header examples, conformance suite (the interim v0.2+ markers come out now the whole suite is v0.2), all three reference servers' VERSION constants, the reference client's accept header, README and implementations directory. S11 gains a two-line version history. Closes #23 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 task
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
1 participant
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.
Summary
Cuts the merged nine-PR fix wave as http-sql v0.2. The wave carries additive changes S11 assigns to a minor bump (the
unsupported_media_typecode) and subtractive MUSTs S11 does not cover (sequential non-atomic execution, REQUIREDstatementIndex, tagged-value emission) that make previously-conforming servers non-conforming -- labeled 0.1 the document contradicted its own wire version. One commit flips everything and removes the interim per-case markers.Acceptance criteria mapping
1. SPEC.md self-references read v0.2, with a version history
Title, status line, registered-type/code preambles, pagination line, S9 wire examples, and all four S10 conformance preambles read v0.2; the S4.2 asymmetry note is reworded version-neutral (nothing about
atomicchanged in 0.2, so pinning it to 0.1 would read as superseded); S11 gains the two-line version history.Evidence: SPEC.md:1, the "### Version history" block under section 11; remaining "0.1" strings are only the 10.1 section number, the past-tense introduction note, and the history line.
2. Conformance suite is the v0.2 suite, markers removed
Preamble reads v0.2; the
(v0.2+)marker on R-4 and its explanatory sentence are deleted; H-1/H-2 expectX-Http-Sql-Version: 0.2.Evidence: conformance/README.md R-4 and H-1/H-2 rows.
3. Examples and directory flip
VERSION constants in all three reference servers, the reference client's accept header, README status/goals headings, and implementations.md spec links all read 0.2.
Evidence:
const VERSION = "0.2"in both Cloudflare servers;X-Http-Sql-Version": "0.2"in reference-server.ts.4. Post-wave coherence verified
Merged 6.1 carries the narrowed
lastInsertIdstring-or-null bullet (the old union string is absent from the file), and the S7 table, 6.2.1, and S10.1 items read coherently after the nine-branch merge sequence.Evidence: grep confirms "OPTIONAL, string or null" present and "string, number, or null" absent in SPEC.md.
Not done
Closes #23
🤖 Generated with Claude Code