docs(release): prep v1.6.8 — feature summary + migration table (PR-1.6.8)#122
Merged
Conversation
5 tasks
…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.
DemchaAV
force-pushed
the
docs/release-1.6.8-prep
branch
from
e2c9ad5 to
71ef280
Compare
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.8 cycle. Replaces the placeholder
"Scope being assembled" intro on the
v1.6.8 — PlannedCHANGELOGentry with a three-paragraph release summary (what shipped /
zero-breaking status / migration), mirroring the structure of
#114 (v1.6.7
release-prep) and #100
(v1.6.6 release-prep).
What this PR adds to CHANGELOG
headline (CV v2 hyperlink-aware project titles + 4 contemporary
BusinessThemepresets + senior-review polish),japicmpverdict (
semver PATCHacross every PR in the cycle), and amigration table.
the senior review during the M3 wiring:
ProjectLabel.parseno longer strips inline Markdown from
title(). Callers thatneed the legacy plain-text projection can wrap with
MarkdownInline.plainText(title), or route through theMarkdownInline.appendpath thatProjectRendereritselfnow uses to get emphasis / link rendering "for free".
What this PR does NOT touch
the right shape from the post-1.6.7 commit (
9e47443f):latest stable v1.6.7 / in develop v1.6.8 / planned v1.7.0.
The
1.6.7→1.6.8version flip in install snippets isthe job of
scripts/cut-release.ps1at cut time.cut-release.ps1against the aggregator.What's in v1.6.8 (PR list since the v1.6.7 cut)
[label](url)parserAfter this PR merges
The v1.6.8 cut runs through the
graphcompose-release-engineerskill:
scripts/cut-release.ps1 -Version 1.6.8— atomic version bumpacross all four poms, flips JitPack snippet to v1.6.8, dates
the CHANGELOG, runs verify, tags
v1.6.8, pushes.release.ymlcreates the GitHub Release from the tag.publish.ymlre-runs verify at the tagged commit and uploadsto Maven Central (Central secrets are wired from v1.6.6 cut).
v1.6.7 → v1.6.8, addv1.6.9 / v1.7.0 — Plannedstub.Test plan
./mvnw test -pl . -Dtest=VersionConsistencyGuardTest,DocumentationCoverageTest,DocumentationExamplesTest— 22 tests, 0 failures.
./mvnw verify -P japicmpwas green at31cacc70(the J-bundle merge that closed the feature scope). This
PR touches only
CHANGELOG.mdprose, so no source/binarysurface change.