chore: cut 0.1.4 and reconcile the changelog against the tag - #271
Merged
Conversation
The Unreleased section stopped short of the tag. Reconciled against `v0.1.3...main` (52 commits), which turned up eleven changes the section did not describe: the semantic language attribute across three grammars and the editor, the marker glued to it, the marker-line block-opener family (a quote, and a %%% comment fence on a list item's and a block quote's marker line), the unterminated %%% run that greyed out the rest of a highlight.js document, the quote caption that is a figure caption again, the spec corpus move to the 22f7f47 freeze, the engine pin move with both ratchets, and the highlighter coverage movement. The section is also condensed. Detail belongs in the tickets, which every entry now references; release notes generated from a section this long are unreadable, and the length is what let entries go missing in the first place. The already-written `0.1.4 - 2026-08-11` section folds into the new one: v0.1.4 was never tagged, so its two entries ship in this release. Its Verification block is dropped - gate results are not consumer-facing. package.json already reads 0.1.4 and is left alone: it was bumped once and never released, and a version is a release artifact rather than a commit counter.
dereuromark
added
chore
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
1 participant
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.
Prepares 0.1.4. No tag, no publish - the maintainer cuts it.
What moved
CHANGELOG.mdonly.package.jsonalready reads0.1.4and is deliberatelyuntouched: it was bumped once, in #210, and never released.
The
## Unreleasedhead becomes## [0.1.4] - 2026-08-18, with a fresh empty## [Unreleased]above it. The already-written## 0.1.4 - 2026-08-11sectionfolds into it -
v0.1.4was never tagged, so the Web Component (#209) and theTiptap type declarations (#208) ship in this release, not a past one. That
section's
### Verificationblock is dropped; gate results are notconsumer-facing.
Reconciled against the tag, not against the last entry
v0.1.3...mainis 52 commits. The section described the second half of themand stopped short, which is the same failure the four core repos hit today.
Eleven changes were missing:
paths (feat: support semantic language attributes #213), and in TextMate, where the construct was also absent from the
shared sweep inventory so all three grammars reported green (feat(textmate): accept the language attribute, and cover it in the sweep #214)
%%%comment fence opened on a list item's marker line (fix: a comment fence opened on a list marker line hides its body #244) and on ablock quote's marker line (fix: a comment fence opened on a block-quote marker line hides its body #246) hides its body
%%%run stops greying out the rest of a highlight.jsdocument (fix: an unterminated %%% run opens nothing in highlight.js #262)
2dc3232e, with both ratchets in bothdirections (chore: move the carve-js engine pin to main, and report both ratchets in both directions #263)
22f7f47freeze, 892 to 1259 documents and 288to 365 categories, with each added category classified (chore: bump the spec corpus to carve 0490ae5, and classify what it added #250, chore: bump the spec corpus to carve 0f6b990, and classify what it added #257, chore: bump the spec corpus to carve 22f7f47, and classify what it added #264)
And condensed
The section ran 286 lines with fenced examples and clause-by-clause
exposition inside individual bullets. It is now one or two lines per change
with the ticket reference that carries the detail. Nothing was dropped in the
shortening - every entry that was there is still there, alongside the eleven
that were not.
Not in this PR
#270 moves the spec pin past the freeze to carve
dc7bb65. It must not landbefore the tag: 0.1.4 is the
22f7f47freeze both grammar repos were pinnedto.