QuantumBFS
register package
Registration pull request created: JuliaRegistries/General/170
After the above pull request is merged, it is recommended that you create a tag on this repository for the registered package version:
git tag -a v0.4.0 -m "<description of version>" 0912b9c5140f92ea9eadf4a4327db811377c9dea
git push origin v0.4.0
Registration pull request created: JuliaRegistries/General/398
After the above pull request is merged, it is recommended that you create a tag on this repository for the registered package version:
git tag -a v0.4.1 -m "<description of version>" 87e2b785ab9b023caf2cac0c361ebaca9b63a2a8
git push origin v0.4.1
Registration pull request created: JuliaRegistries/General/858
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.2 -m "<description of version>" 2091554f2dadccaccc8db2a76a15340d4b24d9ed
git push origin v0.4.2
Registration pull request updated: JuliaRegistries/General/858
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.2 -m "<description of version>" 34c1a38286f23d6d7f870ad5bad3f9405fd717f2
git push origin v0.4.2
Registration pull request updated: JuliaRegistries/General/858
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.2 -m "<description of version>" 5b01922675bf081d3dd6e2fabd6d05178754d764
git push origin v0.4.2
Registration pull request created: JuliaRegistries/General/1070
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.0 -m "<description of version>" 2235804330b0c4cd6d4d1312c4b9aa31d93d7dc5
git push origin v0.5.0
Registration pull request created: JuliaRegistries/General/3041
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.1 -m "<description of version>" b6623c683db5aaaba16cbf36178a0998546021fd
git push origin v0.5.1
Registration pull request created: JuliaRegistries/General/54495
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.7.0 -m "<description of version>" fef45cf841a34596535218297de58d533968adac
git push origin v0.7.0
Registration pull request created: JuliaRegistries/General/54496
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a YaoAPI-v0.2.0 -m "<description of version>" fef45cf841a34596535218297de58d533968adac
git push origin YaoAPI-v0.2.0
Registration pull request created: JuliaRegistries/General/110657
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a YaoPlots-v0.9.3 -m "<description of version>" 9a2fcb9383b6e3adadddb8de74167fa4915a8467
git push origin YaoPlots-v0.9.3
Registration pull request created: JuliaRegistries/General/127195
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a YaoToEinsum-v0.2.5 -m "<description of version>" 0a6cfe9097448eaab7c981170be09513b99f9603
git push origin YaoToEinsum-v0.2.5
Registration pull request created: JuliaRegistries/General/127196
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.1 -m "<description of version>" 0a6cfe9097448eaab7c981170be09513b99f9603
git push origin v0.9.1
Registration pull request created: JuliaRegistries/General/128087
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a YaoBlocks-v0.13.15 -m "<description of version>" 9a0e31397bc97a454eaaacb6f850ceea79d426dc
git push origin YaoBlocks-v0.13.15
Registration pull request created: JuliaRegistries/General/134480
Recommendation: add release notes
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add release notes to this registration, just re-invoke JuliaRegistrator and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a YaoArrayRegister-v0.9.11 -m "<description of version>" 3208bee8f7d1a488d53e1e302b8f9753f8abfc4a
git push origin YaoArrayRegister-v0.9.11
@JuliaRegistrator register subdir=lib/YaoBlocks
Release notes:
Breaking changes
- Refactored the error channel simulation, e.g. renaming UnitaryChannel to MixedUnitaryChannel.