docs(release): prep v1.6.7 — transitive cleanup summary + migration table (PR-1.6.7)#114
Merged
Merged
Conversation
…able (PR-1.6.7) Replaces the placeholder "Scope being assembled" intro on the v1.6.7 — Planned CHANGELOG entry with the actual release summary: - Three-paragraph prose summary (what shipped, zero-breaking status, migration). Mirrors the structure used for v1.6.6 — Planned at cut time (bfaa839 in PR-1.6.6). - Migration table listing every transitive dependency consumers must now declare explicitly: kotlin-stdlib-jdk8, the relevant flexmark-ext-* modules, jackson-dataformat-yaml (YAML configs), jackson-module-jsonSchema, and commons-logging (rare — PDFBox routes via jcl-over-slf4j now, only callers who want the commons-logging API beyond SLF4J need an explicit declaration). - Pulls in the japicmp verdict (semver PATCH, compatible bug fix) so reviewers see at a glance that the I3 NodeRegistry-non-final change is the only surface delta and it's a fix, not a break. README release-status block + install snippets are intentionally not touched here — the post-release-of-1.6.6 commit (6eb4694) already flipped them to the right pre-1.6.7-cut shape (latest stable v1.6.6 / in develop v1.6.7 / planned v1.7.0). The version flip in the install snippets is part of cut-release.ps1 at release time, not this PR. Verification: ./mvnw test -pl . -Dtest=VersionConsistencyGuardTest,DocumentationCoverageTest,DocumentationExamplesTest - 22 tests, 0 failures. The full ./mvnw verify -P japicmp suite was green at b4720c6 (the I3 merge) and this PR touches only CHANGELOG prose.
2 tasks
DemchaAV
added a commit
that referenced
this pull request
Jun 1, 2026
…6.8) Final pre-cut PR for v1.6.8. Replaces the placeholder "Scope being assembled" intro with a three-paragraph release summary (what shipped / zero-breaking status / migration), mirroring the structure of v1.6.7 release-prep (#114) and v1.6.6 release-prep (#100). Headline narrative: CV v2 migration completion (hyperlink-aware project / entry titles via [label](url) inline-Markdown) + four contemporary BusinessTheme presets (nordic/editorial/cinematic/ monochrome) + senior-review follow-ups (registry entry-point symmetry, Dependabot target-branch fix, logback CVE-2026-9828 patch via the deps-sync cherry-pick from #115). Migration table calls out the one semantic shift that surfaced via the CvV2ComponentUtilityTest pin: ProjectLabel.parse no longer strips inline-Markdown from title() — callers that need the legacy plain-text projection can wrap with MarkdownInline.plainText(title), or route through the MarkdownInline.append path that ProjectRenderer itself now uses to get emphasis / link rendering "for free". README release-status block + install snippets are intentionally not touched here — the post-release-of-1.6.7 commit (9e47443) already flipped them to the right pre-1.6.8-cut shape (latest stable v1.6.7 / in develop v1.6.8 / planned v1.7.0). pom version flip in install snippets is part of cut-release.ps1 at release time, not this PR. Verification: ./mvnw test -pl . -Dtest=VersionConsistencyGuardTest,DocumentationCoverageTest,DocumentationExamplesTest - 22 tests, 0 failures. The full ./mvnw verify -P japicmp suite was green at 31cacc7 (the J-bundle merge that closed the feature scope) and this PR touches only CHANGELOG prose.
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.
Summary
Final pre-cut PR for the v1.6.7 dependency-cleanup release.
Replaces the placeholder "Scope being assembled" intro on the
v1.6.7 — PlannedCHANGELOG entry with the actual releasesummary, mirroring the structure used for v1.6.6 release-prep
(#100).
What this PR adds to CHANGELOG
what shipped (transitive cleanup details), zero-breaking status
(japicmp verdict:
semver PATCH, compatible bug fix), andmigration framing.
declare explicitly if they previously got it transitively
through GraphCompose:
kotlin-stdlib-jdk8, the relevantflexmark-ext-*modules,jackson-dataformat-yaml(for YAMLconfigs via
ConfigLoader),jackson-module-jsonSchema, and —rarely —
commons-logging(we exclude it from PDFBox and bridgevia
jcl-over-slf4j; only callers who want thecommons-loggingAPI outside SLF4J routing need an explicitdeclaration).
What this PR does NOT touch
the right shape from the post-1.6.6 commit (
6eb46941): lateststable v1.6.6 / in develop v1.6.7 / planned v1.7.0. The
1.6.6→1.6.7version flip in the install snippets is thejob of
scripts/cut-release.ps1at cut time, not this PR.cut-release.ps1against the aggregator.After this PR merges
The v1.6.7 cut runs through the
graphcompose-release-engineerskill:
scripts/cut-release.ps1 -Version 1.6.7— atomic version bumpacross all four poms via the aggregator, flips JitPack snippet
to v1.6.7, dates the CHANGELOG, runs
verify, tagsv1.6.7,pushes.
release.ymlcreates the GitHub Release from the tag.publish.ymlre-runsverifyat the tagged commit and uploadsto Maven Central (assuming the four Central secrets the v1.6.6
cut wired up are still present).
v1.6.6 → v1.6.7, addv1.6.8 / v1.7.0 — Plannedstub.Test plan
./mvnw test -pl . -Dtest=VersionConsistencyGuardTest,DocumentationCoverageTest,DocumentationExamplesTest— 22 tests, 0 failures.
./mvnw verify -P japicmpwas green atb4720c63(the I3 merge that closed the engineering scope). This PR
touches only
CHANGELOG.mdprose, so no source/binarysurface change.