Create graalvm25.json

[jackkke]

Closes #XXXX

Relates to #XXXX

• I have read the Contributing Guide.

Summary by CodeRabbit

• New Features
  • Added support for GraalVM Community edition 25.0.1 on Windows x64
  • Automatic environment configuration and setup during installation
  • Enabled automated version checking and updates for GraalVM

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new JSON manifest file for GraalVM Community edition 25.0.1 (Windows x64) is introduced, defining package metadata, pre-install configuration steps, environment variable integration (JAVA_HOME, GRAALVM_HOME), and automated version update mechanism via GitHub repository monitoring.

Changes

Cohort / File(s)	Change Summary
GraalVM 25 Manifest bucket/graalvm25.json	New manifest file for GraalVM Community 25.0.1 (Windows x64) with package metadata, download URL, SHA256 hash, PowerShell pre-install steps, environment configuration (JAVA_HOME, GRAALVM_HOME, PATH), and automatic version update integration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify JSON syntax and structure validity
• Confirm SHA256 hash format and download URL correctness
• Validate environment variable configurations (JAVA_HOME, GRAALVM_HOME paths)
• Check autoupdate template URL pattern and GitHub repository reference consistency

Suggested labels

review-needed

Suggested reviewers

• se35710

Poem

🐰 A new manifest hops into place,
GraalVM bundled with grace—
Windows paths aligned just right,
Updates automated day and night!
Checkver keeps it fresh and sound!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is incomplete; it contains only the template placeholders without actual issue references or meaningful context about the changes.	Replace placeholder text with actual issue reference (Closes/Relates to #XXX) and provide a brief description of what graalvm25.json enables or fixes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Create graalvm25.json' clearly describes the primary change—adding a new GraalVM 25 manifest file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

graalvm25

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

Check the full log for details.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 33ad86a and 40ad1e2.

📒 Files selected for processing (1)

• bucket/graalvm25.json (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Pull Requests

bucket/graalvm25.json

[error] 1-1: GraalVM25 Checkver failed. WebClient request error: URL graalvm/graalvm-ce-builds/releases/latest is not valid.

---

[error] 1-1: Process completed with exit code 1.

🔇 Additional comments (2)

bucket/graalvm25.json (2)

20-25: Verify that the hash autoupdate URL is valid.

The autoupdate configuration attempts to fetch the SHA256 hash from $url.sha256 (constructed by appending .sha256 to the release download URL). Please confirm that GraalVM's GitHub releases include a .sha256 file at this location, or adjust the hash fetch strategy if needed.

---

5-5: Correct the license identifier.

GraalVM Community Edition uses the GraalVM Free Terms and Conditions License (GFTCL), not GPL-2.0. This metadata is user-facing and should reflect the actual license.

Apply this diff to correct the license:

-    "license": "GPL-2.0",
+    "license": "GFTCL",

Likely an incorrect or invalid review comment.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Fix checkver configuration—pipeline is failing due to invalid URL construction.

The checkver configuration is incomplete and causing the pipeline to fail. The error indicates the constructed URL graalvm/graalvm-ce-builds/releases/latest is malformed. GraalVM releases use tags like jdk-25.0.1, so you need to specify a regex pattern to extract the version from the release tag.

Apply this diff to fix the checkver configuration:

     "checkver": {
-        "github": "graalvm/graalvm-ce-builds"
+        "github": "graalvm/graalvm-ce-builds",
+        "regex": "jdk-([\\d.]+)"
     },

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"checkver": {
	"github": "graalvm/graalvm-ce-builds"
	},
	"checkver": {
	"github": "graalvm/graalvm-ce-builds",
	"regex": "jdk-([\\d.]+)"
	},

🤖 Prompt for AI Agents

In bucket/graalvm25.json around lines 17-19, the checkver block only specifies
"github" and causes a malformed URL; update the checkver configuration to
include a regex that extracts the version from release tags (which are like
"jdk-25.0.1") so the pipeline builds a correct URL — add a "regex" value that
matches tags starting with "jdk-" and captures the numeric version portion (e.g.
jdk-<version>) and ensure checkver uses release tags for version extraction.