Repository navigation
build: drop the OSSRH publishing block and the ossrh credentials the CI build carried - #11
Merged
Merged
Conversation
…CI build carried OSSRH (oss.sonatype.org) was shut down on 2025-06-30. The repositories block in gradle/publishing.gradle still addressed it and read ossrhUsername/ossrhPassword from the environment while the build was configured, so gradle.yml had to hand the organization's OSSRHUSERNAME/OSSRHPASSWORD secrets to every build, and the secrets cannot be removed from the organization while a build would fail at configuration without them. The block, the two properties naming the variables and the env lines of the workflow go; the resolving repositories in gradle/repositories.gradle are untouched. Publishing to Maven Central goes through the Central Portal, in the family's nmcp form (lightblueseas/email-tails gradle/publishing.gradle), when this repository is next released.
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.
What
gradle/publishing.gradle: therepositories { maven { credentials { ... } setUrl(...) } }block that addressed OSSRH is gone; a comment says where publishing goes now.gradle.properties:projectRepositoriesUserNameKeyandprojectRepositoriesPasswordKeyare gone. The OSSRH URL and name properties stay becausegradle/repositories.gradlestill lists those repositories for resolving..github/workflows/gradle.yml: noossrhUsername/ossrhPasswordenv for the build.Why
OSSRH (oss.sonatype.org) was shut down on 2025-06-30. The block still read
ossrhUsername/ossrhPasswordthroughSystem.getenv(...) ?: project.property(...)while a release build was configured; without a value such a build fails at configuration with a MissingPropertyException, which is why the CI carried the organization'sOSSRHUSERNAME/OSSRHPASSWORDsecrets. Those organization secrets are to be removed; this repository was one of four in lightblueseas whose build read them (measured 2026-10-29 over the workflows of all 86 repositories).Publishing to Maven Central goes through the Central Portal; the family's form is the nmcp setup in lightblueseas/email-tails
gradle/publishing.gradle, to be ported when this repository is next released.Checked:
./gradlew helpevaluates on JDK 21 with Gradle 8.13-rc-2; noossrhorprojectRepositories*Keyleft in gradle, properties or workflow files.🤖 Generated with Claude Code