docs: pivot non-version-locked references to Maven-Central-primary (Phase 1)#103
Merged
Conversation
Phase 1 of the Maven Central coordinate migration: rewrites every forward-facing reference in the documentation and CI infrastructure to describe Maven Central as the canonical install channel, while marking the JitPack URL as legacy (kept resolvable for callers pinned to v1.6.5 and earlier but no longer documented as the recommended path). Version-locked snippets are NOT touched in this commit. The README install section, docs/index.html JSON-LD/install snippets, and the VersionConsistencyGuardTest regex stay on the JitPack format because their value has to equal the current pom.xml version (1.6.5) — a value that does not exist on Maven Central yet. cut-release.ps1 will flip those at v1.6.6 cut time in the release commit; that mechanical swap is Phase 2 of this migration and lands together with the actual Central debut. Files updated: - CONTRIBUTING.md release-flow steps now describe Central publish via .github/workflows/publish.yml; JitPack confirmation removed - ROADMAP.md "Next (v1.7)" entry removed; equivalent "Now (v1.6.x)" entry added noting Central debut in v1.6.6 - SECURITY.md artifacts line points at Central; JitPack noted as legacy-only - docs/README.md release-process pointer mentions Central instead of JitPack - docs/SHOWCASE.md install-snippet description points at Central artefact URL - docs/templates/which-template-system.md "Maven coordinates do not change in 2.0" section reframed Central-first, JitPack as legacy - docs/roadmaps/v1.6-roadmap.md Phase E scope rewritten for Central primary; release-identity coords switched to io.github.demchaav - docs/contributing/release-process.md: top distribution-coordinates block, Phase 2.B post-release verification (Central artefact poll instead of JitPack BUILD SUCCESS), Phase 3 hotfix protocol opener, Section 5 never-do tag-force-move rule, and Section 6 done-criteria all rewritten for Central-primary flow. Historical v1.5.0 / v1.6.5 lessons-learned kept verbatim (accurate to when they happened) - .github/workflows/ci.yml japicmp comment notes Central as baseline source for v1.6.6+, JitPack still serves v1.6.5 - .github/workflows/publish.yml hyphenated-tag comments drop the "go to JitPack" mention; pre-releases ship only to the GitHub Release surface now Guard suite green locally: CanonicalSurfaceGuardTest + DocumentationExamplesTest + DocumentationCoverageTest + VersionConsistencyGuardTest = 30/0/0.
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
Phase 1 of the Maven Central coordinate migration: rewrites every forward-facing reference in documentation and CI infrastructure to describe Maven Central as the canonical install channel, while marking the JitPack URL as legacy (kept resolvable for callers pinned to v1.6.5 and earlier but no longer documented as the recommended path).
Why two phases?
Version-locked snippets — README install section, `docs/index.html` JSON-LD + install snippets, and the `VersionConsistencyGuardTest` regex — stay on the JitPack format in this PR because their value has to equal the current `pom.xml` version (`1.6.5`) and Maven Central does not have 1.6.5 (Central debut is at v1.6.6).
Touching those snippets now would either:
`cut-release.ps1` will perform the JitPack→Central snippet swap at v1.6.6 cut time in the same release commit that bumps the poms. That's Phase 2 of this migration — lands together with the actual Central debut.
What this PR changes
Test plan
Independent from PR-102
This PR is decoupled from #102 (EngineShowcase + hero asset). They can land in any order against `develop`.