adityamparikh opened a new pull request, #238:
URL: https://github.com/apache/solr-mcp/pull/238

   ## What
   
   Provisions GraalVM JDK 25 with GitHub's own `actions/setup-java` 
(`distribution: graalvm`) instead of `graalvm/setup-graalvm`, in `native.yml` 
(all three jobs) and the native-image job of `release-publish.yml`. 
`dev-docs/DEVELOPMENT.md` is updated to match.
   
   ## Why
   
   The ASF Actions allow-list removed `graalvm/setup-graalvm@329c42c` (v1.5.4) 
in apache/infrastructure-actions "Remove Expired Refs" on 2026-09-13. Since 
then every *Native Image* run on a PR has ended in `startup_failure` before any 
job starts (e.g. on #207, #214, #217, #220, #221). The native-image job in 
`release-publish.yml` pins the same SHA, so the next release would fail the 
same way.
   
   Moving to the next allow-listed `setup-graalvm` SHA would only postpone 
this: every remaining pin has an `expires_at` (the newest, v1.6.2, expires 
2026-10-08). GitHub-owned `actions/*` pass the allow-list by pattern, and 
`actions/setup-java` downloads Oracle GraalVM directly, so this pin can't 
expire.
   
   ## Verification
   
   `native.yml` dispatched on the fork at this branch 
([run](https://github.com/adityamparikh/solr-mcp/actions/runs/35952061531)):
   
   - Setup installed `Oracle GraalVM 25.0.4+7.1`
   - `nativeTest`: success (280 run, 0 failed; 138 skipped are the 
`@DisabledInNativeImage` mock tests)
   - native Docker image (stdio) + integration: success
   - native Docker image (http) + integration: success
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


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

Reply via email to