docs(release): binding↔core compatibility note + fold #497 perf into 0.11.0#499
Merged
Merged
Conversation
…try into 0.11.0 Two 0.11 release-prep touch-ups per RELEASING.md: - BINDINGS.md gains the per-binding<->core compatibility note (RELEASING.md 'Across languages'): all registries wrap core 0.11 at 0.11, with the per-registry-patch drift rule spelled out. Cheap insurance ahead of the npm binding's independent patch lane. - CHANGELOG: move the transliterate compose-fusion perf entry (#497) out of [Unreleased] and into [0.11.0], since 0.11.0 is not yet tagged — it ships in the release. Assisted-by: Claude Code:claude-opus-4-8 Signed-off-by: Richard Quinn <quinn.richard@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Doc-only 0.11.0 release-prep updates to keep cross-language release policy and changelog entries aligned as the Node binding opens its own per-registry patch lane.
Changes:
- Added a binding↔core compatibility note/table to
BINDINGS.md, mirroring the “Across languages” policy inRELEASING.md. - Moved the #497 transliterate performance note from
[Unreleased]into the[0.11.0]section inCHANGELOG.md(leaving[Unreleased]empty).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CHANGELOG.md | Reorders headings so the #497 performance bullet lives under 0.11.0 rather than Unreleased. |
| BINDINGS.md | Documents the lockstep-minor / per-registry-patch compatibility rule via a concise compatibility table and guidance. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
0.11 release-prep touch-ups per RELEASING.md (the compliance audit's two follow-ups).
1. Binding↔core compatibility note (exceeds policy)
BINDINGS.md→ Versioning now carries the per-binding↔core compatibility table from RELEASING.md's Across languages section: every registry wraps core 0.11 at 0.11, with the per-registry-patch drift rule (e.g. an npm-only0.11.3) spelled out. The policy says add this "once per-registry patch numbers diverge enough to be confusing" — establishing it now, as the npm binding (0.11's headline) opens its own patch lane, is the cheap insurance the policy recommends.2. Fold the #497 perf entry into 0.11.0
0.11.0 is not yet tagged, so the transliterate compose-fusion recovery (#497) ships in the release. Moved its
### Performancebullet out of[Unreleased](now empty) and into[0.11.0].Doc-only change;
check_doc_claims,audit_language_consistencypass.🤖 Generated with Claude Code