docs: pre-release fixes for v1.8.0#210
Merged
Merged
Conversation
Flip the README "Release status" block so v1.8.0 ("illustrative") is the
Latest stable line — cut-release.ps1 does not touch this block and the
post-release cycle-open commit is develop-only, so it must land on develop
before the cut to reach main. Add the v1.7 -> v1.8 migration guide (additive
only) alongside the prior minor-release guides.
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
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.
Pre-release documentation prep for the v1.8.0 "illustrative" cut (audit-only otherwise — no version bump, no tag; the cut script handles those).
What changed
cut-release.ps1does not touch, and the post-release cycle-open commit that would fix it is develop-only and never reachesmain. Flipping it here, before the cut, is what carries it ontomainin the release commit — otherwisemainkeeps advertising v1.7.1 as latest (the recurring v1.6.9-class bug). Install snippets are left at 1.7.1 on purpose — the script flips those at cut time.docs/roadmaps/migration-v1-7-to-v1-8.md— the v1.7→v1.8 migration guide, matching the priormigration-v1-6-to-v1-7style: additive-only, a table of the new primitives (charts, interpolation modes, sparklines, PathNode, ShapeOutline.Path, SVG import, block alignment, paints), a "things that did NOT break" section, and the one behaviour note (ChartData.Seriesnow rejects non-finite values).Verification
./mvnw verify -pl .→ green (full audit run).CanonicalSurfaceGuardTest,DocumentationCoverageTest,DocumentationExamplesTest,VersionConsistencyGuardTest→ green (no legacy tokens, README/pom still consistent).Note
The README "In develop" line is set to a neutral "next cycle — open" placeholder — no codename invented for the next minor. Adjust if you want a named cycle.