BeiBaiNian opened a new pull request, #48:
URL: https://github.com/apache/casbin-jcasbin-java-cli/pull/48
# Why
The repo currently releases automatically via semantic-release (maven-ci.yml
runs npx semantic-release on every push/PR). As an Apache (incubating) project,
every release must pass a formal vote before publication, so an automatic
release on merge is not compliant:
- merging a PR would trigger an unvoted automatic release
- the release manager must be able to tag release candidates (rc) for the
Apache vote, and only a passed vote may be published as a final tag
This PR replaces the automatic release pipeline with a manual
tag-triggered workflow, aligned with casbin-jcasbin-jdbc-adapter.
# What changed
- Removed .releaserc.json (semantic-release config)
- Removed the "Set up Node.js", "Install semantic-release and plugins" and
"Run semantic-release" steps from .github/workflows/maven-ci.yml (kept the
plain Maven build)
- Added .github/workflows/release.yml, triggered by pushing a git tag:
- vX.Y.Z-rcN -> creates a GitHub pre-release with the Apache source
package (apache-casbin-java-cli-<version>-rcN-incubating-src.tar.gz) for the
vote; nothing is published to Maven Central
- vX.Y.Z -> creates a GitHub release and publishes to Maven Central
- the source package is tar.gz only; no signing, no upload to
dist.apache.org, no extra Apache-side steps
- Added distributionManagement (ossrh) and the maven-gpg-plugin,
maven-javadoc-plugin, maven-source-plugin and central-publishing-maven-plugin
to pom.xml, aligned with casbin-jcasbin-jdbc-adapter
# Verification
- Local `mvn -B package` passes (BUILD SUCCESS); the pom release config does
not break the build
- release.yml / maven-ci.yml parse as valid YAML
- git status shows only the 4 files of this change (examples line-ending
noise reverted)
- No third-party GitHub Actions used - only official actions/checkout,
actions/setup-java and the gh CLI (ASF action whitelist compliant)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
