ProxSuite 0.5.0

[jcarpent]

This release adds support for nonconvex QPs, along with healthy fixes.

What's Changed

• Fix compilation (veg/memory) for gcc 7 and clang 7 by @costashatz in Fix compilation (veg/memory) for gcc 7 and clang 7 #255
• Estimate minimal eigenvalue of quadratic cost hessian by @Bambade in Estimate minimal eigenvalue of quadratic cost hessian #257
• Fix typo Potential typo when computing primal_feasibility_in_rhs_0 in global_primal_residual? #254 by @Bambade in Fix typo #254  #258
• [pre-commit.ci] pre-commit autoupdate by @pre-commit-ci in [pre-commit.ci] pre-commit autoupdate #260
• Sync submodule cmake by @jcarpent in Sync submodule cmake #261

New Contributors

• @costashatz made their first contribution in Fix compilation (veg/memory) for gcc 7 and clang 7 #255

Full Changelog: v0.4.1...v0.5.0

---

This discussion was created from the release ProxSuite 0.5.0.

[stephane-caron]

This automated release note is quite underwhelming: ProxSuite 0.5.0 introduces support for nonconvex QPs, that's a new feature! It should be stated plainly.

(Edit: updated the release note.)

Like changelogs, release notes are for humans, not machines. (Borrowed from Keep a Changelog.) For instance they can be subscribed to to follow new features and changes in a project at release granularity. Automated release notes have some benefits too, but shouldn't we rather append them below a message written by humans for humans?