search

cda-tum / mqt-qao

MQT Quantum Auto Optimizer - A MQT Tool for Solving Optimization Problems with Quantum Computers
MIT License
13 stars 0 forks source link

Bump cda-tum/mqt-workflows from 1.1.5 to 1.2.1 in the github-actions group #25

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the github-actions group with 1 update: cda-tum/mqt-workflows.

Updates cda-tum/mqt-workflows from 1.1.5 to 1.2.1

Release notes

Sourced from cda-tum/mqt-workflows's releases.

MQT Reusable Workflows 1.2.1 Release

👀 What Changed

This follow-up release allows skipping the testing pipeline on the latest supported Python version. Under Linux, this will simply not test under that version, but all other supported versions. Under macOS and Windows, it will test on the minimal supported version and the second latest version supported.

This is especially helpful when new Python versions are released and the ecosystem takes some time to settle and provide wheels for the new version.

The intention would be to enable the skip-testing-latest-python flag once a new Python version is released to get our own wheel builds out as soon as possible. Ideally immediately after that, a follow-up PR (along with a tracking issue) can be created that disables the flag again and that helps to keep track of the progress towards fully supporting new Python versions.

🚀 Features and Enhancements

🤖 CI

Full Changelog: https://github.com/cda-tum/mqt-workflows/compare/v1.2.0...v1.2.1

MQT Reusable Workflows 1.2.0 Release

👀 What Changed

✨ Python 3.13

This release updates cibuildwheel to its latest version, which brings support for building Python 3.13 wheels. Packages that are upgrading to this workflow version should enable the Python 3.13 Trove classifier in their pyproject.toml files, i.e.

classifiers = [
  # ...
  "Programming Language :: Python :: 3.13",
  # ...
]

In addition to the regular wheels, Python 3.13 also includes a free-threaded variant that is built without the global interpreter lock (no-gil). As off now, this has to be explicitly enabled in the cibuildwheel configuration within the pyproject.toml file, i.e.

[tool.cibuildwheel]
# Enable free-threaded support
free-threaded-support = true

Adoption of the free-threaded variant might vary in the beginning. Hence, adopting it in our packages might not be that easy as it will require all dependencies to also be available for the free-threaded variant or to be built from source. Nevertheless, we should try to support it as soon as possible.

⬆️ Dependencies

... (truncated)

Commits
  • fe9af85 ✨ allow skipping testing on latest Python (#19)
  • a7a76e6 Bump pypa/cibuildwheel from 2.19 to 2.20 in the github-actions group (#18)
  • 1045f71 🔧 modify regex to support free-threaded variant
  • db97ced Bump pypa/cibuildwheel from 2.19 to 2.20 in the github-actions group
  • d2c708a ⬆️🪝 update pre-commit hooks (#17)
  • See full diff in compare view


Dependabot compatibility score

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 commands and options
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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
codecov[bot] commented 1 month ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 53.1%. Comparing base (6b5739c) to head (9b45b8d).

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #25 +/- ## ===================================== Coverage 53.1% 53.1% ===================================== Files 6 6 Lines 2815 2815 ===================================== Hits 1496 1496 Misses 1319 1319 ``` | [Flag](https://app.codecov.io/gh/cda-tum/mqt-qao/pull/25/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=cda-tum) | Coverage Δ | | |---|---|---| | [python](https://app.codecov.io/gh/cda-tum/mqt-qao/pull/25/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=cda-tum) | `53.1% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=cda-tum#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

burgholzer commented 1 month ago

This would have needed a bit of work before being merged (as indicated by the release notes) 😢 I knew I should have submitted a review requesting changes 🫠

nquetschlich commented 1 month ago

Sorry for that. I thought it would be okay since all checks were green.

Is this something @DeborahVolpe can look into?

burgholzer commented 1 month ago

Sorry for that. I thought it would be okay since all checks were green.

No worries. Not all updates break things 😉 Can all be "fixed" in a follow-up PR 😌

Is this something @DeborahVolpe can look into?

That would be appreciated. Shouldn't be too hard to adapt. Should also be much easier for pure Python projects. You can have a look at the latest mqt-core PR that adds Python 3.13 support as an inspiration.

DeborahVolpe commented 1 month ago

From the workflow test in the branch seems everything ok and the updates are very minimal. Let me know if additional actions are needed for the merge. I will check for Python 3.13 support