Make JDK25 available for jbang

[koppor]

User description

Fix CI

Follow-up to #14859

Steps to test

Can only be seen in main

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [/] I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

---

PR Type

Enhancement

---

Description

• Add JDK 25 setup to CI workflows for jbang testing

• Configure Corretto distribution with latest version check

• Apply JDK setup to two separate workflow jobs

---

Diagram Walkthrough

flowchart LR
  A["CI Workflows"] --> B["tests-code.yml"]
  B --> C["Add JDK 25 Setup"]
  C --> D["Job 1: Conditional Setup"]
  C --> E["Job 2: Unconditional Setup"]
  D --> F["Corretto Distribution"]
  E --> F
  F --> G["Check Latest Version"]

Loading

File Walkthrough

Relevant files

Configuration changes

tests-code.yml Add JDK 25 setup to workflow jobs                                                .github/workflows/tests-code.yml Added JDK 25 setup step using actions/setup-java@v5 in first job with conditional execution Added JDK 25 setup step in second job without condition Configured Corretto distribution with check-latest: true flag Both setups target Java version '25' for jbang script testing +13/-0

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Use a valid action version Update the actions/setup-java action from the non-existent version @v5 to the latest stable version @v4 to prevent workflow failure. .github/workflows/tests-code.yml [319] -uses: actions/setup-java@v5 +uses: actions/setup-java@v4 Apply / Chat Suggestion importance[1-10]: 10 __ Why: The suggestion correctly identifies that actions/setup-java@v5 is an invalid version, which would cause the entire CI workflow to fail. Correcting it to @v4 is critical for the PR's tests to run.	High
More