docs(publishing): record the 1.9.0 release and its verification - #112
Merged
Merged
Conversation
Verified against what Central serves rather than what was built locally: all 26 coordinates resolve, and baserepo — an AAR module, the case that defeated JitPack twice — serves a sources variant whose file entry keeps the -sources.jar classifier. The jar downloads and contains real Kotlin source. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
WenWe migrated cleanly, but three things came out of it that the other three consumers will hit: FlexiLogger moves 2.1.3 -> 2.1.4. The toolbox's own source is unchanged from 1.8.3 apart from publishing config, so "coordinates only" was how this release was described — including in its release notes, now corrected. That is true of the source and false of the dependency graph: 81d5aac bumped FlexiLogger, and a consumer declaring no version of its own inherits it silently through the layer logging and crash reporting run on. Removing the jitpack.io repository is not a safe default. WenWe still resolves PrefsHelperBase and ComposeReorderable from it, so following that advice blindly would have broken the build. The mavenLocal warning is per-consumer; WenWe never declares it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The Installation heading still read "Add the JitPack repository to your project build file:" above a code block containing mavenCentral() — the sentence and the snippet contradicted each other, and the sentence was the first thing a new consumer read. Also softens the advice about dropping the jitpack.io entry. "Can be removed unless something else needs it" invites skipping the check, and WenWe's migration found it still resolves com.github.projectdelta6:PrefsHelperBase and ComposeReorderable from JitPack — a group that looks deceptively like the toolbox's own old coordinates. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
1.9.0 is released to Maven Central. This records the outcome in the migration doc.
Verified against what Central actually serves, not the local build:
repo1.maven.org.baserepo— an AAR module, the case that defeated JitPack twice — serves areleaseVariantReleaseSourcePublicationvariant whose file entry isbaserepo-1.9.0-sources.jar, classifier intact. This is exactly what JitPack stripped..ktfiles, so it is real source and not an empty placeholder.
Deployment
6dde9178-1023-4072-b6a4-d920bdae35bd, 48/48 components validated, tag1.9.0→e400b22.Remaining: phase 5, migrating the four in-house consumers.
🤖 Generated with Claude Code