chore(sync): reconcile the last four entries with #464 and #466 - #467
Merged
Conversation
`d6c3802a`, `f62aa143` and `aa5f4af0` now point at #466 and its squash SHA `4e42a221`. `07f3fe8d` is reconciled here too, with #464 and `a2d9083d`. That last one is a process slip worth recording: §6 step 4 has each port reconcile the **previous** entry, so #466 should have closed out `07f3fe8d` while it was closing out its own run. It did not, and nothing failed — the ledger simply carried a `pending-merge` on a commit that had shipped two hours earlier. Caught by re-reading the file rather than by a gate; the check is one line and now runs as part of this step. No entry is left unreconciled, and the cursor `aa5f4af0` is upstream HEAD. Bookkeeping only — no source, test or docs change.
5 tasks
IgorShevchik
pushed a commit
that referenced
this pull request
Aug 23, 2026
Only the subject reaches `CHANGELOG.md` — the body is not rendered, breaking
notes aside — so it is the one place a reader of the release notes can be
handed a way back to what was actually ported. Without it a port is
indistinguishable from local work in the only artefact most consumers read.
The subject stays ours. Copying upstream's own first line was the request as
originally put, and it is not what this does: their `Slider` is this fork's
`Range`, and §1 of PORTING.md makes that class of rename mandatory, so their
wording would put a component this library does not ship into our changelog.
The reference points at the commit; the sentence describes what changed here.
fix(Range): forward aria attributes to the thumb (nuxt/ui@d6c3802)
The trigger is a **new key in `processed`**, not the ledger being edited. That
distinction is the whole design: a reconciliation commit — §6 step 4 requires
one whenever a run's last entry has no follower — touches the same file and
ports nothing, and demanding a reference there would be wrong. Checked against
real history rather than fixtures: #467 (bookkeeping) passes, #470 (local work)
passes, #466 and #464 (real ports) are flagged.
Two mistakes worth recording, both of the shape this repository keeps hitting.
The first draft returned an empty array and tested it for truthiness, so every
commit was reported as an unnamed port; running it once was enough. The second
was quieter: without `HEAD^` the check returns nothing and passed silently, and
`actions/checkout` defaults to depth 1 — the same fail-open as the PyYAML
fallback removed in #468. It now warns when it cannot see the previous
revision, and ci.yml fetches depth 2.
`--stdin` skips it: a bare title cannot say what a commit touches, so the
PR-title job checks the parse and the type only. Mutation testing caught that
the case asserting this was vacuous — run from the repository root it passed
whether the guard respected `--stdin` or not, because HEAD there ports nothing.
It now stands on a port revision where the HEAD path does fire.
Refs #437
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012MsMuj8Fic9tjWVjyEyrxc
9 tasks
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
2 participants
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.
Linked issue
Bookkeeping for #464 and #466.
Type of change
Description
d6c3802a,f62aa143andaa5f4af0now point at #466 and its squash SHA4e42a221.07f3fe8dis reconciled here too, with #464 anda2d9083d.That last one is a process slip worth recording.
.sync/PORTING.md§6 step 4 has each port reconcile the previous entry, so #466 should have closed out07f3fe8dwhile it was closing out its own run. It did not, and nothing failed — the ledger simply carried apending-mergeon a commit that had shipped two hours earlier. Caught by re-reading the file, not by a gate.No entry is left unreconciled, and the cursor
aa5f4af0is upstream HEAD, so the sync queue is empty.Bookkeeping only — no source, test or docs change.
Checklist
Generated by Claude Code