Skip to content

release: v3.0.0 - #948

Merged
gsdali merged 1 commit into
mainfrom
release/v3.0.0
Aug 18, 2026
Merged

release: v3.0.0#948
gsdali merged 1 commit into
mainfrom
release/v3.0.0

Conversation

@gsdali

@gsdali gsdali commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

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 the v3.0.0 release asset.
  • CLAUDE.md: the pin paragraph names the release asset rather than the pre-release.

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 rather than taken from the comment.

Expect swift build to fail on this PR, and why

Package.swift now names an asset that does not exist yet. Package.swift's own sequencing note describes this window:

There is a window between 1 and 2 where the URL 404s. It is unavoidable and it is short; what matters is checking step 3 rather than assuming.

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-scripts is 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 main at 99269293

check result
full swift test 5618 tests / 1461 suites / 0 failures
10 gate scripts + 9 --self-tests all exit 0
count-operations 4339, matches README and API_REFERENCE
CHANGELOG transcription audit 0 entries missing
docs/SEMVER.md v3.0.0 3 rows, 2 subsections (#844, #943)
patches: disk / enumeration / prose 17 / 17 / seventeen
tsan-stress.sh not required — no lock, atomic or thread-local added or removed since v2.0.0; all 90 concurrency-shaped diff lines are clang-format reindentation

Do not delete v3.0.0-kernel.1

Every 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 bisect and 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#v300 with migrations. This commit adds no new API change.

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>
@gsdali
gsdali merged commit 0c9f927 into main Aug 18, 2026
5 of 6 checks passed
@kilo-code-bot

kilo-code-bot Bot commented Aug 18, 2026

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)
  • CLAUDE.md
  • Package.swift
  • docs/CHANGELOG.md

Reviewed by nemotron-3-ultra-550b-a55b:free · Input: 150.9K · Output: 1.8K · Cached: 260.9K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant