Publish to Maven Central only - #49
Merged
Merged
Conversation
Every release was going to two registries with the same six artifacts. GitHub Packages requires authentication even for a public package, so nobody was depending on Kdrant through it; it was a second place to keep in sync and no second way to consume the library. The publishing block goes from all seven modules and the step from the release workflow, which drops the packages permission with it. Versions up to 1.2.0 stay where they are: unpublishing them would break anyone who did wire up a token, for no gain.
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.
Every release was carrying the same six artifacts to two registries. GitHub Packages requires a token
even for a public package, so nobody was depending on Kdrant through it — it was a second place to keep
in sync and no second way to consume the library. Maven Central is the channel, and now it is the only
one.
publishing { repositories { maven { name = "GitHubPackages" … } } }block is gone from all sevenpublished modules.
Publish to GitHub Packagesstep is gone fromrelease.yml, and thepackages: writepermissionwith it. What remains is assemble → attest → publish to Maven Central.
./gradlew tasks --allno longer lists a…GitHubPackagesRepositorytask anywhere.Versions up to and including
1.2.0stay on GitHub Packages. Unpublishing them would break anyonewho did wire up a token, for no gain; this only stops adding new ones.