docs(readme): v1.9.1 release status + graph-compose-markdown companion#314
Merged
Conversation
Flip the Release-status blockquote to name v1.9.1 as latest stable (the inline-code column-wrap fix) so the release commit carries it to main, and add graph-compose-markdown to Companion projects — a Markdown input surface built on the engine, published on Maven Central (io.github.demchaav:graph-compose-markdown), linked to its Central artifact page since it has no public repo.
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.
Why
Pre-release documentation for v1.9.1 (the inline-code column-wrap fix, already on
develop). Two by-hand docs the release script does not touch: the "Release status" prose block (which must reachmainvia the release commit — process gate 2.8 / the v1.6.9 lesson) and surfacing thegraph-compose-markdowncompanion as a Markdown input path.What changed
cut-release.ps1only rewrites the install snippets, not this block, so it must land ondeveloppre-cut so the release commit carries it tomain.io.github.demchaav:graph-compose-markdown:0.3.0). Linked to the Central artifact page — the parser has no public GitHub repo, so a GitHub link would 404.Verification
Release-readiness audit on
develop+ this change:./mvnw -B -ntp clean verify -pl .→ BUILD SUCCESS, 1634 tests, 0 failures (guard suite incl.VersionConsistencyGuardTest/DocumentationCoverageTest/CanonicalSurfaceGuardTest; install snippets untouched, stay1.9.0).GenerateAllExamples→ 87 generated, no layout errors.developcurrent withmain; tagv1.9.1absent; README relative links resolve.Lane: docs — pre-release prep, no code/API change. Merge on
developbefore runningcut-release.ps1 -Version 1.9.1.