🔖 Prepare release of v1.3.1

[denialhaag]

This PR prepares the release of v1.3.1, which adds support for multiple new LLVM versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a v1.3.1 release entry to CHANGELOG.md (dated 2026-05-18) with PR references, updates README GitHub Action examples to use setup-mlir@v1.3.1, and bumps package.json version to 1.3.1.

Changes

Release 1.3.1 updates

Layer / File(s)	Summary
Changelog entry and PR links CHANGELOG.md	Adds ## [1.3.1] - 2026-05-18 under Unreleased, updates the [unreleased] compare link to v1.3.1...HEAD, and adds PR reference link definitions for #177, #174, #171, #155, #146, and #134.
README action examples update README.md	Bumps GitHub Actions examples munich-quantum-software/setup-mlir@v1.3.0 → @v1.3.1 in the "Set up MLIR" and "Set up MLIR (Debug) (Windows Only)" snippets.
Package version bump package.json	Increment package version field from 1.3.0 to 1.3.1.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• munich-quantum-software/setup-mlir#31: Similar release/version wiring changes across CHANGELOG.md, README, and package.json.
• munich-quantum-software/setup-mlir#123: Also updates package.json version and README action examples for a release bump.
• munich-quantum-software/setup-mlir#110: Previous release-prep bump touching changelog and release-facing documentation.

Suggested reviewers

• burgholzer

Poem

🐰 I hopped to the changelog, inked a date,
Bumped the package, kept examples straight,
PR links aligned like carrots in a row,
A tiny release, neat and low—hooray, let's go! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title states 'Prepare release of v1.3.1' but the PR objectives indicate this is preparing a v1.4.0 release. The file changes show version bumps to 1.3.1, creating a significant discrepancy between the title and PR objectives.	Clarify the intended release version. Either update the PR title to 'Prepare release of v1.4.0' to match the PR objectives, or update the PR objectives and files to reflect v1.3.1 if that is the intended version.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The pull request description mentions preparing release v1.3.1 with LLVM support, which aligns with the changelog and version bump changes in the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch prepare-release-v1.4.0

---

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.}

[burgholzer]

LGTM, but why is this a minor version bump if the only updates are new LLVM versions? Shouldn't this simply be 1.3.1?

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 3: Update the package.json version field to match the PR release target
v1.4.0 by changing the "version" property value from "1.3.1" to "1.4.0" so
package metadata aligns with the PR and release artifacts; locate and update the
"version" key in package.json accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2adade3c-c8ef-45c7-9d8e-6b2ca4af82ae

📥 Commits

Reviewing files that changed from the base of the PR and between a42c3da and 7c752ae.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• CHANGELOG.md
• README.md
• package.json

[denialhaag]

LGTM, but why is this a minor version bump if the only updates are new LLVM versions? Shouldn't this simply be 1.3.1?

I honestly just went with the release draft. I really don't know why Release Drafter thinks this would be a minor release. The configuration looks good to me, and no PR is labeled as "minor." 🤔

That said, I have made this a patch release now and will release it as such. 😌

[denialhaag]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

CodeRabbit did not approve the PR after resolving its comment