slachiewicz opened a new pull request, #519:
URL: https://github.com/apache/commons-crypto/pull/519

   
   - Update runners from ubuntu-20.04 to ubuntu-latest, use modern macOS 
versions
   - Add timeout limits to prevent stuck jobs
   - Embed OpenSSL path discovery directly in adhoctest.yml
   - Update Java test matrix to include Java 25
   - Change JDK distribution from temurin to zulu for better compatibility
   - Improve macOS OpenSSL detection with unified path logic
   - Add Maven cache configuration via setup-java action
   - Fix pom.xml test-with-jar profile configuration
   
   Thanks for your contribution to [Apache 
Commons](https://commons.apache.org/)! Your help is appreciated!
   
   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? For commit messages
   - [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.
   - [ ] 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