Checklist for preparing and publishing a new release of org.kobjects.parsek:core.
Configure Maven Central Portal and GPG signing credentials in ~/.gradle/gradle.properties (outside the repository):
mavenCentralUsername=<sonatype-portal-token-username>
mavenCentralPassword=<sonatype-portal-token-password>
signing.keyId=<gpg-key-id>
signing.password=<gpg-key-passphrase>
signing.secretKeyRingFile=/path/to/secring.gpg-
Clean up previous deprecations
- Remove
@DeprecatedAPIs kept for one release cycle in the previous version. - Ensure any newly replaced APIs are marked
@Deprecated(withReplaceWithwhere helpful).
- Remove
-
Bump version & update docs
- Update
org.kobjects.parsek.versioningradle.properties. - Add an entry under
## Version HistoryinREADME.md. - Update
core/module.mdandREADME.mdif packages, examples, or links changed.
- Update
-
Verify build & tests across all targets
./gradlew check :core:publishToMavenLocal --warning-mode all
- Confirm zero unexpected compiler/Gradle warnings and inspect
~/.m2/repository/org/kobjects/parsek/.
- Confirm zero unexpected compiler/Gradle warnings and inspect
-
Commit, tag, and push
git add -A git commit -m "Release X.Y.Z" git tag vX.Y.Z git push && git push --tags
-
Publish to Maven Central
./gradlew :core:publishToMavenCentral
automaticRelease = trueis configured incore/build.gradle.kts, so Central Portal will validate and publish automatically.
-
Update hosted Dokka documentation
./gradlew :core:dokkaGenerate
- Upload the generated
core/build/dokka/directory tohttps://kobjects.org/parsek/dokka/. - Spot-check the links in
README.md(both Dokka links and the Maven Central badge).
- Upload the generated