-
Notifications
You must be signed in to change notification settings - Fork 8
feat!: Rename tket2* libs to tket* #987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #987 +/- ##
=======================================
Coverage 79.65% 79.65%
=======================================
Files 94 94
Lines 11549 11552 +3
Branches 11279 11282 +3
=======================================
+ Hits 9199 9202 +3
Misses 1720 1720
Partials 630 630
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This PR contains breaking changes to the public Rust API. cargo-semver-checks summary
|
CodSpeed Performance ReportMerging #987 will create unknown performance changesComparing Summary
Benchmarks breakdown
|
rename tket2-hseries to |
Couple of mentions of "Tket2" in |
I ignored the example notebooks, since they are based on an already old version of tket2 (they depend on published libs rather that the local ones). |
Co-authored-by: Alec Edgington <54802828+cqc-alec@users.noreply.github.com>
I reckon we should update extension names (could be in a separate PR though). |
Looks like we all agree on that. I'll do it in a separate PR. |
In contrast to #987, this is not a breaking API change but a breaking _serialization_ change. I bumped the extension versions even if not strictly necessary. BREAKING CHANGE: Renamed the `tket2.*` HUGR extensions to `tket.*`
This affects both rust and python libraries. Since we are renaming the main packages, I just renamed all the sub-crates / libs too to keep thing consistent and reduce confusion. Extension names have **not** been updated, as I worry about further breakage. Should we update them (in a separate PR)? ### Project breakage - For dependents, the breakage should be limited to having to update the dependency names and some types like `Tk2Op` to `TketOp`, `TKET2_EXTENSION` to `TKET_EXTENSION`, etc. - For the local automation, I tried to update the workflows as much as possible, but we can only test them once merged. - `release-please`'s manifest has been updated. I'll recreate the last python release tags without the `2`, and the workflow should pick up from there. We'll need to swap some pypi API keys before merging the release PR. - `release-plz` will probably get confused with which commits should be picked. - ~It also does not have permission to publish new crates, so we'll need to manually push `tket-hseries` and update the API keys.~ - Both the `tket` and `tket-qsystem` crates have been created and setup for trusted publishing, so the release should work correctly. ### Follow up and deprecation. We'll need to make patch releases for the `tket2*` libraries adding a deprecation warning to the README and directing users to the new libraries. - Por python, take a look at the `pypi-rename` [README template](https://github.com/simonw/pypi-rename/blob/main/%7B%7Bcookiecutter.old_package_name%7D%7D/README.md). - For rust, make sure to update both the README and `lib.rs` rusdocs. - Rustdoc recently added support for warning boxes: [rust-lang/rust#106561](https://www.github.com/rust-lang/rust/pull/106561) BREAKING CHANGES: Yes BREAKING CHANGE: Libraries renamed from `tket2*` to `tket*` --------- Co-authored-by: Alec Edgington <54802828+cqc-alec@users.noreply.github.com>
In contrast to #987, this is not a breaking API change but a breaking _serialization_ change. I bumped the extension versions even if not strictly necessary. BREAKING CHANGE: Renamed the `tket2.*` HUGR extensions to `tket.*`
## 🙂 New release * `tket2`: 0.12.3 -> `tket` 0.13.0 (New crate name!) * `tket2-hseries`: 0.16.1 -> `tket-qsystem` 0.17.0 (New crate name!) <details><summary><i><b>Changelog</b></i></summary><p> ## `tket` <blockquote> ## [0.13.0](tket2-v0.12.3...tket-v0.13.0) - 2025-07-25 ### New Features - [**breaking] Rename tket2.* HUGR extensions to tket.* ([#988](#988)) - [**breaking] Rename tket2* libs to tket* ([#987](#987)) - [**breaking**] Update to `hugr 0.21` ([#965](#965)) - Add guppy extension with drop operation ([#962](#962)) - [**breaking**] Split the pytket extension encoder trait ([#970](#970)) </blockquote> ## `tket-qsystem` <blockquote> ## [0.17.0](tket2-hseries-v0.16.1...tket-qsystem-v0.17.0) - 2025-07-25 ### New Features - [**breaking] Rename tket2.* HUGR extensions to tket.* ([#988](#988)) - [**breaking] Rename tket2* libs to tket* ([#987](#987)) - [**breaking**] Update to `hugr 0.21` ([#965](#965)) - Add guppy extension with drop operation ([#962](#962)) </blockquote> </p></details> --- This PR was generated by a human.
🤖 I have created a release *beep* *boop* --- ## [0.10.0](tket-exts-v0.9.2...tket-exts-v0.10.0) (2025-07-29) ### ⚠ BREAKING CHANGES * Renamed the `tket2.*` HUGR extensions to `tket.*` * Libraries renamed from `tket2*` to `tket*` ### Features * **py:** update hugr-py dependency to 0.13 ([#996](#996)) ([1bf4c70](1bf4c70)) * Rename `tket2.*` HUGR extensions to `tket.*` ([#988](#988)) ([c5279c5](c5279c5)) * Rename tket2* libs to tket* ([#987](#987)) ([450f06a](450f06a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
🤖 I have created a release *beep* *boop* --- ## [0.5.0](tket-eccs-v0.4.0...tket-eccs-v0.5.0) (2025-07-29) ### ⚠ BREAKING CHANGES * Renamed the `tket2.*` HUGR extensions to `tket.*` * Libraries renamed from `tket2*` to `tket*` ### Features * Rename `tket2.*` HUGR extensions to `tket.*` ([#988](#988)) ([c5279c5](c5279c5)) * Rename tket2* libs to tket* ([#987](#987)) ([450f06a](450f06a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: Seyon Sivarajah <seyon.sivarajah@cambridgequantum.com>
🤖 I have created a release *beep* *boop* --- ## [0.12.0](tket-py-v0.11.1...tket-py-v0.12.0) (2025-07-29) ### ⚠ BREAKING CHANGES * Renamed the `tket2.*` HUGR extensions to `tket.*` * Libraries renamed from `tket2*` to `tket*` ### Features * **py:** update hugr-py dependency to 0.13 ([#996](#996)) ([1bf4c70](1bf4c70)) * Rename `tket2.*` HUGR extensions to `tket.*` ([#988](#988)) ([c5279c5](c5279c5)) * Rename tket2* libs to tket* ([#987](#987)) ([450f06a](450f06a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: Seyon Sivarajah <seyon.sivarajah@cambridgequantum.com> Co-authored-by: Seyon Sivarajah <seyon.sivarajah@quantinuum.com>
This affects both rust and python libraries. Since we are renaming the main packages, I just renamed all the sub-crates / libs too to keep thing consistent and reduce confusion. Extension names have **not** been updated, as I worry about further breakage. Should we update them (in a separate PR)? ### Project breakage - For dependents, the breakage should be limited to having to update the dependency names and some types like `Tk2Op` to `TketOp`, `TKET2_EXTENSION` to `TKET_EXTENSION`, etc. - For the local automation, I tried to update the workflows as much as possible, but we can only test them once merged. - `release-please`'s manifest has been updated. I'll recreate the last python release tags without the `2`, and the workflow should pick up from there. We'll need to swap some pypi API keys before merging the release PR. - `release-plz` will probably get confused with which commits should be picked. - ~It also does not have permission to publish new crates, so we'll need to manually push `tket-hseries` and update the API keys.~ - Both the `tket` and `tket-qsystem` crates have been created and setup for trusted publishing, so the release should work correctly. ### Follow up and deprecation. We'll need to make patch releases for the `tket2*` libraries adding a deprecation warning to the README and directing users to the new libraries. - Por python, take a look at the `pypi-rename` [README template](https://github.com/simonw/pypi-rename/blob/main/%7B%7Bcookiecutter.old_package_name%7D%7D/README.md). - For rust, make sure to update both the README and `lib.rs` rusdocs. - Rustdoc recently added support for warning boxes: [rust-lang/rust#106561](https://www.github.com/rust-lang/rust/pull/106561) BREAKING CHANGES: Yes BREAKING CHANGE: Libraries renamed from `tket2*` to `tket*` --------- Co-authored-by: Alec Edgington <54802828+cqc-alec@users.noreply.github.com>
In contrast to #987, this is not a breaking API change but a breaking _serialization_ change. I bumped the extension versions even if not strictly necessary. BREAKING CHANGE: Renamed the `tket2.*` HUGR extensions to `tket.*`
## 🙂 New release * `tket2`: 0.12.3 -> `tket` 0.13.0 (New crate name!) * `tket2-hseries`: 0.16.1 -> `tket-qsystem` 0.17.0 (New crate name!) <details><summary><i><b>Changelog</b></i></summary><p> ## `tket` <blockquote> ## [0.13.0](tket2-v0.12.3...tket-v0.13.0) - 2025-07-25 ### New Features - [**breaking] Rename tket2.* HUGR extensions to tket.* ([#988](#988)) - [**breaking] Rename tket2* libs to tket* ([#987](#987)) - [**breaking**] Update to `hugr 0.21` ([#965](#965)) - Add guppy extension with drop operation ([#962](#962)) - [**breaking**] Split the pytket extension encoder trait ([#970](#970)) </blockquote> ## `tket-qsystem` <blockquote> ## [0.17.0](tket2-hseries-v0.16.1...tket-qsystem-v0.17.0) - 2025-07-25 ### New Features - [**breaking] Rename tket2.* HUGR extensions to tket.* ([#988](#988)) - [**breaking] Rename tket2* libs to tket* ([#987](#987)) - [**breaking**] Update to `hugr 0.21` ([#965](#965)) - Add guppy extension with drop operation ([#962](#962)) </blockquote> </p></details> --- This PR was generated by a human.
🤖 I have created a release *beep* *boop* --- ## [0.10.0](tket-exts-v0.9.2...tket-exts-v0.10.0) (2025-07-29) ### ⚠ BREAKING CHANGES * Renamed the `tket2.*` HUGR extensions to `tket.*` * Libraries renamed from `tket2*` to `tket*` ### Features * **py:** update hugr-py dependency to 0.13 ([#996](#996)) ([1bf4c70](1bf4c70)) * Rename `tket2.*` HUGR extensions to `tket.*` ([#988](#988)) ([c5279c5](c5279c5)) * Rename tket2* libs to tket* ([#987](#987)) ([450f06a](450f06a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
🤖 I have created a release *beep* *boop* --- ## [0.5.0](tket-eccs-v0.4.0...tket-eccs-v0.5.0) (2025-07-29) ### ⚠ BREAKING CHANGES * Renamed the `tket2.*` HUGR extensions to `tket.*` * Libraries renamed from `tket2*` to `tket*` ### Features * Rename `tket2.*` HUGR extensions to `tket.*` ([#988](#988)) ([c5279c5](c5279c5)) * Rename tket2* libs to tket* ([#987](#987)) ([450f06a](450f06a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: Seyon Sivarajah <seyon.sivarajah@cambridgequantum.com>
🤖 I have created a release *beep* *boop* --- ## [0.12.0](tket-py-v0.11.1...tket-py-v0.12.0) (2025-07-29) ### ⚠ BREAKING CHANGES * Renamed the `tket2.*` HUGR extensions to `tket.*` * Libraries renamed from `tket2*` to `tket*` ### Features * **py:** update hugr-py dependency to 0.13 ([#996](#996)) ([1bf4c70](1bf4c70)) * Rename `tket2.*` HUGR extensions to `tket.*` ([#988](#988)) ([c5279c5](c5279c5)) * Rename tket2* libs to tket* ([#987](#987)) ([450f06a](450f06a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: Seyon Sivarajah <seyon.sivarajah@cambridgequantum.com> Co-authored-by: Seyon Sivarajah <seyon.sivarajah@quantinuum.com>
This affects both rust and python libraries.
Since we are renaming the main packages, I just renamed all the sub-crates / libs too to keep thing consistent and reduce confusion.
Extension names have not been updated, as I worry about further breakage.
Should we update them (in a separate PR)?
Project breakage
For dependents, the breakage should be limited to having to update the dependency names and some types like
Tk2Op
toTketOp
,TKET2_EXTENSION
toTKET_EXTENSION
, etc.For the local automation, I tried to update the workflows as much as possible, but we can only test them once merged.
release-please
's manifest has been updated. I'll recreate the last python release tags without the2
, and the workflow should pick up from there. We'll need to swap some pypi API keys before merging the release PR.release-plz
will probably get confused with which commits should be picked.It also does not have permission to publish new crates, so we'll need to manually pushtket-hseries
and update the API keys.tket
andtket-qsystem
crates have been created and setup for trusted publishing, so the release should work correctly.Follow up and deprecation.
We'll need to make patch releases for the
tket2*
libraries adding a deprecation warning to the README and directing users to the new libraries.pypi-rename
README template.lib.rs
rusdocs.BREAKING CHANGES: Yes
BREAKING CHANGE: Libraries renamed from
tket2*
totket*