ppkarwasz opened a new pull request, #417:
URL: https://github.com/apache/commons-build-plugin/pull/417

   This goal generates a [SLSA](https://slsa.dev/) build attestation and 
attaches it to the build as a file with the `.intoto.json` extension.
   
   The attestation records the following information about the build 
environment:
   
   - The Java version used (vendor, version string)
   - The Maven version used
   - The `gitTree` hash of the unpacked Java distribution
   - The `gitTree` hash of the unpacked Maven distribution
   
   The `gitTree` hashes uniquely and verifiably identify the exact content of 
the Java and Maven distributions used during the build, independently of how or 
where they were obtained. This allows consumers of the attestation to verify 
that the build
   environment matches a known distribution.
   
   Before you push a pull request, review this list:
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [x] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [x] I used AI to create any part of, or all of, this pull request. Which 
AI tool was used to create this pull request, and to what extent did it 
contribute? I used Claude Code for the initial version of most code, followed 
by a manual review.
   - [x] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself.
   - [x] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. This may not always be possible, 
but it is a best practice.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.
   


-- 
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]

Reply via email to