chore: describe the 0.1.6 delta in the changelog - #96
Merged
Conversation
The Unreleased section carried only the engine-bundle fix. Reconciling it against the five squash merges since 0.1.5 found three grammar narrowings with no entry at all - each of them a scope a user sees directly, and each closing a false positive the 0.1.5 notes had recorded as unfixable in a golden. The vendor-address change is left undescribed: it is contact metadata on the marketplace page, not behavior anyone installing the plugin observes. The existing engine-bundle entry is condensed, keeping both facts it carried - the 42-commit gap and the provenance test that could not see it.
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.
Reconciles the changelog against every squash merge since
0.1.5, ahead of a0.1.6draft. No source, no version field, no tag.git log 0.1.5..origin/main --oneline --mergesis empty - every merge on this repo is a squash - so the enumeration is the plain log.{_x}stops scoping as an attribute block,{_x_}reads as the underline the author meant|=hot= is the reading |no longer colors as a header cell holdinghot=; the alignment run gets a scope for the first timeThe three added entries close #85, #86 and #87 - the false positives the
0.1.5notes recorded because a golden would have pinned the wrong answer. Those recordings shipped in0.1.5; the fixes ship here, so nothing has to move out of the released section.Also checked, and clean: no entry in the
0.1.5section names a PR that merged after the tag. The JCEF fix it claims (#88) looks absent fromgit log 0.1.4..0.1.5by PR number, butcarve-jcef.xmlwas added by the release-prep PR #89 itself, so it did ship.Validation split: this is a changelog-only diff, so there is nothing a local suite could exercise that CI does not. No Gradle build was started -
gate-runon this repo discovers five Gradle tasks and one of them wants a JDK this host does not have, and none of them readCHANGELOG.md. The spec submodule was left uninitialized for the same reason: nothing on this branch reads the corpus.