⬆️👨‍💻 Update munich-quantum-toolkit/workflows action to v1.14

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
munich-quantum-toolkit/workflows	action	minor	v1.12 -> v1.14

---

Release Notes

munich-quantum-toolkit/workflows (munich-quantum-toolkit/workflows)

v1.14

Compare Source

📚 Refer to the GitHub Release Notes for previous changelogs.

v1.13

Compare Source

📚 Refer to the GitHub Release Notes for previous changelogs.

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[burgholzer]

This looks good. 👍🏼
It might be worth running the C++ repos with the extensive tests enabled once. So that we can be sure that the respective builds work, or if we should disable some.

For that, you would have to add the respective *-extensive-* labels and then push some dummy change to trigger CI.
If some of the checks fail (like macos-15 for example, let's create a tracking issue for that and exclude the configuration)

[denialhaag]

This looks good. 👍🏼 It might be worth running the C++ repos with the extensive tests enabled once. So that we can be sure that the respective builds work, or if we should disable some.

For that, you would have to add the respective *-extensive-* labels and then push some dummy change to trigger CI. If some of the checks fail (like macos-15 for example, let's create a tracking issue for that and exclude the configuration)

Good point! I triggered extensive tests here and for QMAP. 👍