azure-quantum-python icon indicating copy to clipboard operation
azure-quantum-python copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

Bump cirq-core from 0.15.0 to 1.0.0 in /azure-quantum

Open dependabot[bot] opened this issue 3 years ago • 0 comments

Bumps cirq-core from 0.15.0 to 1.0.0.

Release notes

Sourced from cirq-core's releases.

Cirq v1.0.0

What's new

Cirq has officially left alpha and is v1.0. With this release comes new policies on API stability as well as functionality gaurantees for the long term. Along with some minor bug fixes and tweaks, this release focuses on stabilizing the APIs within cirq-core. With cirq-core we intend to follow along with semver and only make breaking changes with moves to new major versions. For the vendor packages we plan to continue to allow developers to iterate at speed and will do best effort on ensuring any API changes come with as little friction as possible. For all the details on this policy please see: release.md.

To make this upgrade as smooth as possible, we recommend first upgrading your installation to Cirq v0.15 to surface any deprecation warnings or upcoming breakages you might experience, once those are resolved, you can safely install Cirq v1.0.0.

Thank you all so much for your hard work.

What's Changed

... (truncated)

Changelog

Sourced from cirq-core's changelog.

Versioning and Releases

Cirq is currently (as of May 2020) alpha, and so has a MAJOR version of 0. Below is info on how we version releases, and how the releases themselves are created. Note that development is done on the master branch, so if you want to use a more stable version you should use one of the releases or install from pypi using pip install cirq. The release from the latest commit to master can be installed with pip install --pre cirq.

Versioning

We follow semantic versioning for labeling our releases. Versions are labeled MAJOR.MINOR.PATCH where each of these is a numerical value. The following guarantees are provided:

  1. All packages released at the same time from the Cirq repository will share the same Semantic Versioning 2.0.0 number.
    1. Packages may have different version numbers in the future, at which point this policy will be updated.
  2. Libraries in the cirq-core directory (with the exception of cirq-core/cirq/contrib) adhere to the guarantees outlined in the Semantic Versioning specification. In summary: “Bug fixes not affecting the API increment the patch version, backwards compatible API additions/changes increment the minor version, and backwards incompatible API changes increment the major version.”
  3. The contrib directory (at cirq-core/cirq/contrib) follows Semantic Versioning except the MINOR version increment policy: releases with MINOR version increments may contain backward-incompatible functionality changes to its public API.
    1. May be changed to strictly follow Semantic Versioning in the future, at which point this policy will be updated.
  4. Cirq vendor directories (cirq-aqt, cirq-google, cirq-ionq, etc.) follow Semantic Versioning except the MINOR version increment policy: each vendor directory has a separate policy on whether MINOR version increments provide backward-compatibility guarantees, as described in version_policy.md in the respective directory.
    1. If version_policy.md does not exist in a particular vendor directory, MINOR version increments may contain backward-incompatible functionality changes to its public API.
    2. For each vendor directory, version policies may be modified to strictly follow Semantic Versioning in the future.
  5. Versions based on unreleased branches of master will be suffixed with ".dev".

The rules for version changes are:

  • Increment the PATCH version if all changes are bug fixes only.
  • Increment the MINOR version if changes contain functionalities which are backward-compatible, or if a vendor directory or contrib contains backward-incompatible changes and the policy for the directory allows backward-incompatible changes for a minor version increment.

... (truncated)

Commits
  • 506ef08 Removing v0.16.0dev -> v1.0.0
  • beab8b7 Refactor AbstractControlValues and it's implementations to fix multiple bugs ...
  • 3c67cd7 Suppress matplotlib warnings on non-GUI use of show() (#5749)
  • e0ae7ca Use GoogleCZTargetGateset; add device gateset as additional gates in target g...
  • 27b5d4b Fix classically controlled op Moment diagram (#5777)
  • adff66e Remove unused qid_shape param from DMSimState.init (#5792)
  • 9f5e234 Always return 1D vector from final_state_vector (#5793)
  • e362cb6 pytest exclude TestNoiseProperties from test discovery (#5791)
  • 80b335b Handle global phase gate in single-qubit merge transformers (#5786)
  • 7062846 GoogleCZTargetGateset (#5744)
  • Additional commits viewable 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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependabot[bot] avatar Jul 19 '22 08:07 dependabot[bot]