chore[build]: Use sbt-ci-release #124
Conversation
This simplifies the release process, and updates to work with the new "Central Portal" for Maven Central. Hopefully this fixes publishing the package ot maven central.
There was a problem hiding this comment.
Pull Request Overview
This PR modernizes the Maven Central publishing workflow by migrating from manual PGP and Sonatype plugins to the automated sbt-ci-release plugin, which supports the new Central Portal publishing method.
Key changes:
- Replaces sbt-pgp and sbt-sonatype plugins with sbt-ci-release
- Updates sbt version from 1.10.7 to 1.11.7
- Simplifies CI workflow by replacing custom publishing script with single ci-release command
Reviewed Changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| project/build.sbt | Consolidates publishing plugins by replacing sbt-pgp and sbt-sonatype with sbt-ci-release |
| project/build.properties | Updates sbt to version 1.11.7 to support the new plugin |
| admin/build.sbt | Removes custom Sonatype publishing configuration now handled by sbt-ci-release |
| .github/workflows/ci.yml | Simplifies release workflow by replacing manual PGP import and conditional publishing logic with automated ci-release command |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
aegbert5
left a comment
aegbert5
left a comment
There was a problem hiding this comment.
Changes make sense to me. Is there a way to test these changes before merging? Or do we need to merge first?
|
I can test that the normal build works (as you can see by the passing checks), but unfortunately, there isn't really a good way to test the deployment part without merging. |
This simplifies the release process, and updates to work with the new "Central Portal" for Maven Central.
Hopefully this fixes publishing the package ot maven central.