release: v3.0.0 - #948
Merged
Merged
Conversation
Stamps the release. `docs/CHANGELOG.md`'s `## Unreleased` becomes `## v3.0.0` and `## Current:` moves off v2.0.0; `Package.swift` and CLAUDE.md re-point at the v3.0.0 release asset. `checksum:` deliberately does NOT change. The v3.0.0 asset is the byte-identical v3.0.0-kernel.1 zip re-uploaded (149,067,826 bytes, sha256 77df5a0ae860b0f947353ff6eabf0ab25eb810ef0ce135b56bc60ff1e3e52ef2), so only `url:` moves. That is the shape v2.0.0 used with its own kernel.3 asset, re-verified against both live assets during this release. Do not delete v3.0.0-kernel.1 afterwards: every commit in the window between the rebuild and this one pins it, so deleting it takes its asset and makes those commits unbuildable from a clean checkout. Two breaking changes, both with migrations in docs/SEMVER.md#v300: the #844 enum rename, and #943's six bounding-box accessors becoming Optional. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Reviewed by nemotron-3-ultra-550b-a55b:free · Input: 150.9K · Output: 1.8K · Cached: 260.9K |
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.
What
The v3.0.0 release commit.
docs/CHANGELOG.md:## Unreleased→## v3.0.0, and## Current:moves off v2.0.0 with a summary of what this release is.Package.swift:url:re-pointed at thev3.0.0release asset.CLAUDE.md: the pin paragraph names the release asset rather than the pre-release.checksum:deliberately does not changeThe v3.0.0 asset is the byte-identical
v3.0.0-kernel.1zip re-uploaded — 149,067,826 bytes, sha25677df5a0ae860b0f947353ff6eabf0ab25eb810ef0ce135b56bc60ff1e3e52ef2— so onlyurl:moves. That is the shape v2.0.0 used with its own kernel.3 asset, re-verified against both live assets during this release rather than taken from the comment.Expect
swift buildto fail on this PR, and whyPackage.swiftnow names an asset that does not exist yet.Package.swift's own sequencing note describes this window:The tag has to point at the commit carrying the swapped URL, so the commit must exist before the release can be cut from it.
gate-scriptsis the required check and is pure Python, so it passes. The build jobs go green once the release is created and the asset uploaded, which is the immediate next step.Release verification, already done on
mainat99269293swift test--self-testscount-operationsAPI_REFERENCEdocs/SEMVER.mdv3.0.0tsan-stress.shDo not delete
v3.0.0-kernel.1Every commit between the kernel rebuild and this one pins that pre-release. Deleting it takes its asset with it and makes that window unbuildable from a clean checkout, which breaks
git bisectand any historical re-measurement.CHANGELOG entry
None. This PR is the CHANGELOG stamp.
SemVer impact
This is the release itself. The two breaks it ships are #844 (enum rename) and #943 (six bounding-box accessors become Optional), both already recorded in
docs/SEMVER.md#v300with migrations. This commit adds no new API change.