doc: correct the 2.0.0 changelog against the tags (#85491) - #268
Merged
Conversation
Audited every claim in the 2.0.0 entry against the tree at the 1.29.0 and 2.0.0 tags instead of against the draft it grew from. Four entries did not belong to the release: - Voice Family settings module. The module is in the tree at 1.29.0 (51 files including its route file, factory, filter and both locale files) and is the headline item of the 1.29.0 release notes. 2.0.0 only fixed its VoiceBindingsList provide, which stays listed under Fixed. - mainFileInternal asset filter. Added by #253 on 11 March, three months before the 1.29.0 tag. Internal-image support is older still (1.26.0). - Public export create binding to a licences array. #256 is the commit the 1.29.0 tag points at, so it shipped there. - "vue-router 4 to 5" is wrong: 1.29.0 already ran ^5.0.2 and 2.0.0 runs ^5.2.0, which the dependency list in the same file stated correctly. The breaking change is the file-based routing, not a major bump. Both #84735 references leave 2.0.0 with the first and third item; that work item belongs entirely to 1.29.0. The mainFileInternal filter was never documented in any release, so it is added to the 1.29.0 entry where it actually shipped.
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.
Audited every claim in the 2.0.0 entry against the tree at the
1.29.0and2.0.0tags instead ofagainst the draft it grew from. Four entries did not belong to the release.
voiceFamilyin the tree at1.29.0, incl.src/router/routes/coreDam/voiceFamily.ts; the headline item of the 1.29.0 release notes. No commit in1.29.0..2.0.0introduces it — 2.0.0 only fixed itsVoiceBindingsListprovide, which stays under Fixed.mainFileInternalasset filterd1bf1825(#253) merged 2026-03-11, the1.29.0tag is 2026-06-15. Internal-image support is older still (1.26.0).6e0bb204(#256) is the commit the1.29.0tag points at (same timestamp). Listed in the 1.29.0 notes too.1.29.0already ran^5.0.2,2.0.0runs^5.2.0— the dependency list in the same file said so correctly. The breaking change is the file-based routing, not a major bump.Both
#84735references were among these, so that work item now belongs entirely to 1.29.0.The
mainFileInternalfilter was never documented in any release — it is added to the 1.29.0 entry,where it actually shipped.
Everything else in the entry was verified as correct: active-filter chips, oxlint/oxfmt, lightningcss,
eslint-plugin-vuetify, unplugin-auto-import, file-based routing (66
definePagepages), the anzuESLint plugin, the
validateAllguard, manual chunking,watch-common-admin, breadcrumbs, the labsmigration (175 files), the
src/views→src/domainsmove (421 → 0 / 0 → 644), filter persistence on22 datatables, the removed
shortestDimensionfilter and Prettier, the nginx/assetsfix, themeta.createi18n keys, and the Vuetify 3 → 4 and pinia 3 → 4 bumps.No code changes, no new version. The 2.0.0 release body links to the file pinned at the
2.0.0tag,so it is repointed at
mainafter this merges, otherwise the release page keeps serving the old text.