🔖 Prepare release of 2025.11.25

[denialhaag]

This PR prepares the release of the initial version, 2025.11.25.

[coderabbitai]

📝 Walkthrough

Walkthrough

A version bump updating package version and example release tags from 2025.11.24 to 2025.11.25 across package metadata, action metadata, GitHub Actions workflow, and README examples.

Changes

Cohort / File(s)	Change Summary
Package metadata package.json	Updated version field from 2025.11.24 to 2025.11.25.
Action metadata action.yml	Updated input/example release-tag text from 2025.11.24 to 2025.11.25.
Workflow .github/workflows/build-portable-mlir-toolchain.yml	Updated release-tag example text from 2025.11.24 to 2025.11.25.
Documentation README.md	Replaced occurrences of 2025.11.24 with 2025.11.25 in examples and installation commands.

Sequence Diagram(s)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Spot-check: package.json (version), action.yml (input description), .github/workflows/build-portable-mlir-toolchain.yml, and README.md for any missed tag occurrences.

Poem

🐰 I nudged the tag up one small stride,

From twenty-four to twenty-five I glide.
A hop in package, docs, and flow—
Tiny change, and onward I go. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main purpose of the changeset: preparing a release for version 2025.11.25, which aligns with all the version updates across multiple files.
Description check	✅ Passed	The description is directly related to the changeset, stating that the PR prepares the release of version 2025.11.25, which matches the version updates documented in the file summaries.
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
• Commit unit tests in branch prepare-release

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3cfc591 and 2c79a9c.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• .github/workflows/build-portable-mlir-toolchain.yml (1 hunks)
• README.md (2 hunks)
• action.yml (1 hunks)
• package.json (1 hunks)

🔇 Additional comments (4)

package.json (1)

3-3: Version bump is appropriate and properly isolated.

The package version has been updated to reflect the new release, with all dependencies remaining stable. This is the correct approach for a release preparation.

action.yml (1)

22-22: Example input updated correctly.

The tag input description example now references the new release version, ensuring users have current guidance.

.github/workflows/build-portable-mlir-toolchain.yml (1)

15-15: Workflow input description example updated correctly.

The release-tag input example now references the new version, providing accurate guidance for manual workflow execution.

README.md (1)

11-11: All version references successfully updated to 2025.11.25 with no missed instances.

Verification confirms that no references to the old version (2025.11.24) remain in the codebase. The README has been comprehensively updated across all user-facing documentation and installation examples, ensuring consistent guidance for users.

---

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

[burgholzer]

LGTM and ready to go. Once CI is green, we should be able to start the release process, right?

[denialhaag]

LGTM and ready to go. Once CI is green, we should be able to start the release process, right?

Yes, I would say so!