Hi,

I'd like to share the work on the Trusted Publishing proof of concept for
Maven projects (
https://github.com/apache/tooling-trusted-releases/issues/1844).

Repository: https://github.com/apache/tooling-atr-maven-example

The goal is to show that an ASF Maven project can make a release from
GitHub Actions with the standard Maven release process and push it to ATR
with Trusted Publishing, without personal tokens.

Done so far:

- The ATR project is created from .asf.yaml.
- A small multi-module Maven project using the ASF parent POM and its
push-to-atr profile.
- A GitHub workflow that runs mvn verify.
- A release workflow that runs release:prepare and release:perform. The
first release, 1.0.0, was made with it.
- The build uses the latest SNAPSHOT of atr-maven-plugin for testing
purposes.

Not enabled yet:

- Signing and deployment to the repository. Postponed to the next phase.
- Pushing to ATR. The plugin runs in dry run mode, waiting for OIDC support.

Next steps:

1. I will work on adding GitHub OIDC support to atr-maven-plugin, so it can
log in to ATR without a personal token.
2. Turn off dry run and push a real release to ATR.
3. Add a CI job that checks build reproducibility.

Comments and ideas are welcome.

--
Sławomir Jaranowski

Reply via email to