Bump cvxpy from 1.1.12 to 1.2.1

[dependabot]

Bumps cvxpy from 1.1.12 to 1.2.1.

Release notes

Sourced from cvxpy's releases.

v1.2.1

CVXPY 1.2.1 is a patch release (i.e., a bugfix release) in the 1.2.X release series. Special thanks to @​mkoeppe for his contribution!

Changes since 1.2.0:

• Web documentation updates (#1731).
• More web doc updates (#1732).
• Fix sign error with log_sum_exp (#1689).
• Handle new CyLP statuses from coin-or/CyLP#150 (#1707), from @​mkoeppe.
• Fix TypeError in GLOP and PDLP interfaces (#1736).
• Update error message for mixed-integer problems (#1738).
• Propagate SCIP interface bugfix from PR (#1739).

v1.2.0

CVXPY 1.2

This release marks a big milestone in CVXPY's development. It's the first time we've incremented the minor version number since releasing CVXPY 1.1 in June 2020. Since then we've added many new features and improved CVXPY's efficiency in important ways. A summary of those changes -- including many which were released with little fanfare between CVXPY 1.1.1 and 1.1.18 -- can be found on cvxpy.org. Changes specific to CVXPY 1.2 include:

• Four new and improved "atoms" for use in optimization modeling: xexp, partial_trace, partial_transpose, and kron. The latter three atoms significantly expand CVXPY's modeling capabilities for matrix representations of tensor products; they'll be especially useful for quantum information applications.
• Two new interfaces to numerical solvers. CVXPY can now interface with Google OR Tools to call GLOP and PDLP.
• Support for Python versions 3.7 to 3.10.

We've also grown in ways that can't be seen from changes to source code alone. We've adopted open governance principles, become a NumFOCUS affiliated project, and -- starting this week -- we're adopting semantic versioning.

Semantic versioning

Our adoption of semantic versioning will fundamentally change the way we approach CVXPY's maintenance and development. The most observable change is that new features will only be released in major or minor releases, as opposed to patch releases. Since CVXPY receives new feature contributions on a regular basis, that means you can expect minor releases from us much more often: multiple times per year instead of once in two years. It also means we'll support multiple minor-release series at any given time. Right now we provide bugfix support for CVXPY 1.1 and 1.2. Once CVXPY 1.3 comes out later this year, we'll provide bugfix support for CVXPY 1.1, 1.2, and 1.3.

While this approach creates more work for day-to-day maintenance, it has two major benefits:

1. It gives us space to heavily refactor CVXPY's back-end for improved efficiency in the future. This will be important for CVXPY users who want to scale their convex optimization workflows to larger and more sophisticated problems.

2. It makes it easier for us to publicly recognize and encourage CVXPY's many volunteer contributors. This is crucial for the long-term health of CVXPY as an open-source software project.

Our adoption of semantic versioning is an ongoing process. Stay tuned for announcements on our Discord server, website, or Twitter for more information.

Who made this possible?

CVXPY 1.2.0 includes contributions from 15 people across more than 25 pull requests. In no particular order, those contributors are

• @​phschiele (PRs #1607, #1617, #1624, #1628)
• @​xinyueshen (PR #1660)
• @​allenlawrence94 (PR #1621)
• @​lochsh (PR #1677)
• @​PTNobel (PR #1648)
• @​Michael-git96 (PR #1684)
• @​chrisyeh96 (PR #1616)
• @​TimonKnigge (PRs #1637, #1646)
• @​dcajasn (PR #1640)
• @​parthb83 (PRs #1641, #1683)

... (truncated)

Commits

• d275ee4 release v1.2.1
• 447ad28 Propagate SCIP interface bugfix from PR #1739
• ea2e288 update error message for mixed-integer problems (#1738)
• b08cf98 fix TypeError in GLOP and PDLP interfaces (#1736)
• 4732838 Handle new CyLP statuses from coin-or/CyLP#150 (#1707)
• 55f1fa8 Fix sign error with log_sum_exp (#1689)
• d724a21 remove out of date news
• 9a7e9a3 Stevens suggestions
• 4321100 More web doc updates (#1732)
• c8d61fa web documentation updates (#1731)
• Additional commits viewable in compare view

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)