docs(release): cover #314 stricter validation + #316 linux-arm64 in v0.8.0 notes - #320
Merged
Conversation
…0.8.0 notes Two changes landed after the version-bump commit (#313) that wrote the v0.8.0 release notes, so they were undocumented: - #314 unified constraint validation across the loader, mutation, and merge surfaces. Its behavior changes are all stricter (enum enforced on merge, cross-version @unique rejection, precise within-batch vs across-batch dup-key semantics, per-table overwrite validation) and are user-visible, so they get a dedicated section. - #316 added linux-arm64 (aarch64) as a first-class prebuilt target + Homebrew bottle; note the new platform. Also mention the stricter validation in the release intro. Docs-only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…state Greptile P2: the prior wording implied a live-head @unique guarantee, but #314's check is snapshot-scoped (probes the write's pinned base view via the @key/@unique BTREEs), so a concurrent writer committing the same value after the base was opened is not caught — matching the 'full cross-version uniqueness is still a gap' note in docs/dev/invariants.md. Qualify with 'visible to that write'. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
The v0.8.0 release notes (
docs/releases/v0.8.0.md) were written in theversion-bump commit (#313). Two user-relevant changes landed on
mainafterthat commit, so they are currently undocumented in the notes:
changes are all stricter (none relaxed): enum now enforced on the merge path,
cross-version
@uniquecollisions now rejected, precise within-batch vsacross-batch duplicate-
@keysemantics, and per-table overwrite validation.These are user-visible and can newly reject inputs that previously slipped
through, so they get a dedicated "Stricter, unified constraint validation"
section.
archive + Homebrew bottle; documented as a new platform.
Also adds a one-clause mention of the stricter validation to the release intro.
Docs-only; no code changes. This is the last content gap before cutting the
v0.8.0tag from the currentmaintip.🤖 Generated with Claude Code
Greptile Summary
This PR updates the v0.8.0 release notes. The main changes are:
Confidence Score: 5/5
This looks safe to merge.
Important Files Changed
Reviews (2): Last reviewed commit: "docs(release): scope cross-version uniqu..." | Re-trigger Greptile
Context used: