As I already wrote a few times, if you want to work on automating release 
process with GHA, you'll have better flexibility and Tooling support by using 
Tooling GHA actions instead of trying to add more features to atr-maven-plugin

but yes, playing at Tooling level with proof of concept of releasing with ATR 
a project that uses Maven is great to discover and share experience: we have 
most prerequisites in place.

Based on this, we'll see at Maven project level what we do on our own full 
release process [1]

My key personal question is: what does trigger the release?
Do you expect that the release manager still uses "mvn release:prepare" on his 
machine or do something else?

Notice: given this test is very Tooling oriented, and every project at ASF 
that uses Maven will be interested , not only the Maven project (even if we 
are key SMEs), we'll need to make sure wider community is involved.

Regards,

Hervé


[1] 
https://maven.apache.org/developers/release/maven-project-release-procedure.html

Le mardi 17 novembre 2026, 22:03:02 heure normale d’Europe centrale Slawomir 
Jaranowski a écrit :
> 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





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to