Bump cda-tum/mqt-core from 2.4.1 to 2.4.2 in the github-actions group (…

…#332)

Bumps the github-actions group with 1 update:
[cda-tum/mqt-core](https://github.com/cda-tum/mqt-core).

Updates `cda-tum/mqt-core` from 2.4.1 to 2.4.2
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/cda-tum/mqt-core/releases">cda-tum/mqt-core's
releases</a>.</em></p>
<blockquote>
<h2>MQT Core 2.4.2 Release</h2>
<h2>👀 What Changed</h2>
<p>Small patch release with updated reusable workflow. Apple Silicon
runners now also support Python 3.8 and 3.9.
Python tests are now run on:</p>
<ul>
<li>all supported Python versions on Ubuntu</li>
<li>the minimum and maximum supported version on macOS (Intel + arm64)
and Windows.</li>
</ul>
<p>This means that, e.g., for a library that supports Python 3.8 to
3.12, 5+2+2+2=11 test runs will be started and will produce coverage
reports. If you update to the new version of the workflows, make sure to
adjust the codecov config.</p>
<h2>📄 Documentation</h2>
<ul>
<li>🍱 MQT Branding on RtD <a
href="https://github.com/burgholzer"><code>@​burgholzer</code></a> (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/603">#603</a>)</li>
<li>🍱 Use centralized images from MQT repository <a
href="https://github.com/burgholzer"><code>@​burgholzer</code></a> (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/602">#602</a>)</li>
</ul>
<h2>🤖 CI</h2>
<ul>
<li>👷🔧🍎 enable Python 3.8+ tests on macos-14 runners <a
href="https://github.com/burgholzer"><code>@​burgholzer</code></a> (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/597">#597</a>)</li>
</ul>
<h2>⬆️ Dependencies</h2>
<ul>
<li>⬆️🪝 update pre-commit hooks <a
href="https://github.com/pre-commit-ci"><code>@​pre-commit-ci</code></a>
(<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/598">#598</a>)</li>
<li>⬆️🪝 update pre-commit hooks <a
href="https://github.com/pre-commit-ci"><code>@​pre-commit-ci</code></a>
(<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/595">#595</a>)</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/cda-tum/mqt-core/compare/v2.4.1...v2.4.2">https://github.com/cda-tum/mqt-core/compare/v2.4.1...v2.4.2</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/cda-tum/mqt-core/commit/63051e8f6558f24f7d12baf6bae898c68cd620e3"><code>63051e8</code></a>
🍱 MQT Branding on RtD (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/603">#603</a>)</li>
<li><a
href="https://github.com/cda-tum/mqt-core/commit/d958662eacf8759f55cd05b65e008db332c363ee"><code>d958662</code></a>
:pencil2: fix link</li>
<li><a
href="https://github.com/cda-tum/mqt-core/commit/7389edba06521ccefb44bba16cc85f0e15650ab4"><code>7389edb</code></a>
🍱 Use centralized images from MQT repository (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/602">#602</a>)</li>
<li><a
href="https://github.com/cda-tum/mqt-core/commit/8fbfaa5283e8a4c42ddb768a6bf59c3751ac4443"><code>8fbfaa5</code></a>
👷🔧🍎 enable Python 3.8+ tests on macos-14 runners (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/597">#597</a>)</li>
<li><a
href="https://github.com/cda-tum/mqt-core/commit/8d0746c12bddaf9c2a96bf9c7b54a148cb720d2c"><code>8d0746c</code></a>
⬆️🪝 update pre-commit hooks (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/598">#598</a>)</li>
<li><a
href="https://github.com/cda-tum/mqt-core/commit/5a15e5d06ee3e5fb555de828a449ab7dd157e5e9"><code>5a15e5d</code></a>
⬆️🪝 update pre-commit hooks (<a
href="https://redirect.github.com/cda-tum/mqt-core/issues/595">#595</a>)</li>
<li>See full diff in <a
href="https://github.com/cda-tum/mqt-core/compare/v2.4.1...v2.4.2">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cda-tum/mqt-core&package-manager=github_actions&previous-version=2.4.1&new-version=2.4.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

.github/workflows/cd.yml

@@ -7,7 +7,7 @@ on:
 jobs:
   python-packaging:
     name: 🐍 Packaging
-    uses: cda-tum/mqt-core/.github/workflows/reusable-python-packaging.yml@v2.4.1
+    uses: cda-tum/mqt-core/.github/workflows/reusable-python-packaging.yml@v2.4.2
     with:
       pure-python: true
 

.github/workflows/ci.yml

@@ -14,21 +14,21 @@ concurrency:
 jobs:
   change-detection:
     name: 🔍 Change
-    uses: cda-tum/mqt-core/.github/workflows/reusable-change-detection.yml@v2.4.1
+    uses: cda-tum/mqt-core/.github/workflows/reusable-change-detection.yml@v2.4.2
 
   python-tests:
     name: 🐍 Test
     needs: change-detection
     if: fromJSON(needs.change-detection.outputs.run-python-tests)
-    uses: cda-tum/mqt-core/.github/workflows/reusable-python-ci.yml@v2.4.1
+    uses: cda-tum/mqt-core/.github/workflows/reusable-python-ci.yml@v2.4.2
     secrets:
       token: ${{ secrets.CODECOV_TOKEN }}
 
   code-ql:
     name: 📝 CodeQL
     needs: change-detection
     if: fromJSON(needs.change-detection.outputs.run-code-ql)
-    uses: cda-tum/mqt-core/.github/workflows/reusable-code-ql-python.yml@v2.4.1
+    uses: cda-tum/mqt-core/.github/workflows/reusable-code-ql-python.yml@v2.4.2
 
   required-checks-pass: # This job does nothing and is only used for branch protection
     name: 🚦 Check