Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(deps): Bump cda-tum/mqt-workflows from 1.3 to 1.4 in the github…
…-actions group (#69) Bumps the github-actions group with 1 update: [cda-tum/mqt-workflows](https://github.com/cda-tum/mqt-workflows). Updates `cda-tum/mqt-workflows` from 1.3 to 1.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/cda-tum/mqt-workflows/releases">cda-tum/mqt-workflows's releases</a>.</em></p> <blockquote> <h2>MQT Reusable Workflows 1.4.0 Release</h2> <h2>👀 What Changed</h2> <p>This release refactors the way tests on Python are distributed and run. Instead of running separate sessions for each Python version, this PR changes the workflows to run all sessions in a single workflow run per operating system. This should allow for maximum caching reuse across builds and reduce the number of CI runners that need to be waited for. It also reduces the number of macOS runners requested per CI run, which is now fixed to 2 for the python tests regardless of the number of supported Python versions.</p> <p>While, previously, only the <code>ubuntu-latest</code> runner would run tests on all Python versions, this PR changes the workflows so that also macOS and Windows runners test all the versions. This should not cause a noticable runtime increase given the excessive caching opportunities, both via <code>ccache</code> and <code>uv</code>.</p> <blockquote> <p>[!IMPORTANT]<br /> This change will require consuming workflows to adapt their configuration!</p> <p>The <code>skip-testing-latest-python</code> workflow input has been removed and the Python versions being tested are solely defined by the nox sessions configuration. Consequently, if a package should not be tested under Python 3.13 yet for example, <code>"3.13"</code> should be removed from the <code>PYTHON_ALL_VERSIONS</code> array in the <code>noxfile.py</code>.</p> </blockquote> <p>In addition, this release switches to the official <code>setup-uv</code> action and employs <code>uv</code> in a couple more places (see <a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/31">#31</a> for further details).</p> <h2>🚀 Features and Enhancements</h2> <ul> <li>♻️ unify Python testing <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/32">#32</a>)</li> <li>⚡ use official <code>setup-uv</code> action and more of <code>uv</code> <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/31">#31</a>)</li> <li>🚸 no longer need to explicitly provide <code>GITHUB_TOKEN</code> to <code>setup-z3</code> <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/30">#30</a>)</li> </ul> <h2>🤖 CI</h2> <ul> <li>♻️ unify Python testing <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/32">#32</a>)</li> <li>⚡ use official <code>setup-uv</code> action and more of <code>uv</code> <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/31">#31</a>)</li> </ul> <h2>⬆️ Dependencies</h2> <!-- raw HTML omitted --> <ul> <li>Bump pypa/cibuildwheel from 2.20 to 2.21 in the github-actions group <a href="https://github.com/dependabot"><code>@dependabot</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/33">#33</a>)</li> <li>♻️ unify Python testing <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/32">#32</a>)</li> <li>⚡ use official <code>setup-uv</code> action and more of <code>uv</code> <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/31">#31</a>)</li> <li>🚸 no longer need to explicitly provide <code>GITHUB_TOKEN</code> to <code>setup-z3</code> <a href="https://github.com/burgholzer"><code>@burgholzer</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/30">#30</a>)</li> <li>Bump peter-evans/create-pull-request from 6 to 7 in the github-actions group <a href="https://github.com/dependabot"><code>@dependabot</code></a> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/29">#29</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-workflows/issues/28">#28</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-workflows/issues/27">#27</a>)</li> </ul> <!-- raw HTML omitted --> <p><strong>Full Changelog</strong>: <a href="https://github.com/cda-tum/mqt-workflows/compare/v1.3.2...v1.4.0">https://github.com/cda-tum/mqt-workflows/compare/v1.3.2...v1.4.0</a></p> <h2>MQT Reusable Workflows 1.3.2 Release</h2> <h2>👀 What Changed</h2> <p>A small bugfix release for the MQT Core Update workflow.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/cda-tum/mqt-workflows/commit/7bc94c4133e6849d3e6503b717ff470fb752b5a4"><code>7bc94c4</code></a> Bump pypa/cibuildwheel from 2.20 to 2.21 in the github-actions group (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/33">#33</a>)</li> <li><a href="https://github.com/cda-tum/mqt-workflows/commit/c256b51441fdf2e8bb11d1f2e66edf3028897f12"><code>c256b51</code></a> ♻️ unify Python testing (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/32">#32</a>)</li> <li><a href="https://github.com/cda-tum/mqt-workflows/commit/0b6eabc6083793121777d2e18ff5e99e0878a329"><code>0b6eabc</code></a> ⚡ use official <code>setup-uv</code> action and more of <code>uv</code> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/31">#31</a>)</li> <li><a href="https://github.com/cda-tum/mqt-workflows/commit/fdc30c7975f9cb39ffe964703d5084e3171052de"><code>fdc30c7</code></a> 🚸 no longer need to explicitly provide <code>GITHUB_TOKEN</code> to <code>setup-z3</code> (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/30">#30</a>)</li> <li><a href="https://github.com/cda-tum/mqt-workflows/commit/dba77f053b165199edd988cf09241a92d72063f8"><code>dba77f0</code></a> Bump peter-evans/create-pull-request from 6 to 7 in the github-actions group ...</li> <li><a href="https://github.com/cda-tum/mqt-workflows/commit/8dea125a6d32c96930430a76362ba3e8316886a5"><code>8dea125</code></a> ⬆️🪝 update pre-commit hooks (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/28">#28</a>)</li> <li><a href="https://github.com/cda-tum/mqt-workflows/commit/38b81a0148818efff3d8eac03c7c802986aaafbd"><code>38b81a0</code></a> ⬆️🪝 update pre-commit hooks (<a href="https://redirect.github.com/cda-tum/mqt-workflows/issues/27">#27</a>)</li> <li>See full diff in <a href="https://github.com/cda-tum/mqt-workflows/compare/v1.3...v1.4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cda-tum/mqt-workflows&package-manager=github_actions&previous-version=1.3&new-version=1.4)](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>
- Loading branch information