Repository navigation
Prepare 1.10.0 minor release metadata - #100
Merged
Merged
Conversation
Report CLI version 1.10.0 with its deterministic source identity and regression assertion. Finalize the 1.10.0 changelog entry (including the unpublished 1.9.1 hygiene items), add minor release notes for exact interchange and a 1.10 qualification record with the API compatibility check, and mark 1.10.0 prepared in the roadmap and authority records. Public APIs and finite budgets are unchanged. Publication remains separate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Release preparation for 1.10.0 — exact interchange. It follows the pattern of #85 (1.9.0). Public APIs and finite budgets are unchanged. No tag or publication follows from this PR.
1.10.0. The regression assertion inIntegrationTestsis updated and the CLI source identity regenerated.platform-floorlane, CLI identity without DocC, developer kit 0.2.0) move into it.Documentation/ReleaseNotes/1.10.0.mdcovering canonical JSON (RFC 8785),JSONEnvelope,JSONPatch.difference, the JSONHTML difference page, RFC 7464 text sequences, maintenance, platforms and compatibility.Documentation/Qualification/Release1.10.mdwith scope per PR (docs: record the approved 1.9.1–2.0.0 release train #94–Add JSONEnvelope, a versioned digest-checked envelope over JCS #99), the API compatibility check, fixed format commitments, lane receipts and open items.AGENTS.md,Documentation/README.mdandReleaseLines.mdmark 1.10.0 as prepared.API compatibility
I ran
swift package diagnose-api-breaking-changes 1.9.0. It exits 1 with two findings, both onpackagedeclarations in JSON, which #95 gave a defaultedchargesOutputparameter:JSONNumber.binaryConversionText(meter:)JSONNumber.doubleValue(policy:meter:)These are not public API, so they are false positives for consumers, as with the package-only finding for 1.9.0. The other eleven modules report no breaking change.
Qualification (local)
Toolchain: Apple Swift 6.4.2 (swiftlang-6.4.2.1.9), macOS 27.3. Source:
deb16f5;ad1c863adds only the receipts to the record.python3 Scripts/ci.py --lane docs: exit 0, 4/4.python3 Scripts/ci.py --lane native, first run: exit 1.qualify_cli_limits.pytimed out (30 s) on one CLI subprocess at host load ~56. Run alone, that call took 9 ms and the script passed 33/33.nativererun on the same commit: exit 0, 62/62, 0 failed.Open before tagging (maintainer decisions)
wasmwas not run locally).🤖 Generated with Claude Code