Bodhi 5.7.0 in Staging

[Ryan Lerch <rlerch@xxxxxxxxxx>]

The newest version of Bodhi (5.7.0) is now available in staging, and ready to be tested out:

https://bodhi.stg.fedoraproject.org/

This minor release of Bodhi comes with a handful of new features and bugfixes, including:

Features

========
* Query different Greenwave contexts for critical path updates, allowing for
stricter policies to apply https://github.com/fedora-infra/bodhi/pull/4180
* Use Pagure's hascommit new endpoint API to check user's rights to
create/edit updates. This allow collaborators to push updates for releases
for which they have commit access. https://github.com/fedora-infra/bodhi/pull/4181

Bug fixes
=========

* Fixed an error about handling bugs in automatic updates https://github.com/fedora-infra/bodhi/pull/4170
* Side-tag wheren't emptied when updates for current releases were pushed to
stable https://github.com/fedora-infra/bodhi/pull/4173

* Bodhi will avoid sending both 'update can now be pushed' and 'update has been
pushed' notifications at the same time on updates pushed automatically
https://github.com/fedora-infra/bodhi/issue/3846
* Clear request status when release goes EOL https://github.com/fedora-infra/bodhi/issue/4039
* Allow bodhi to not operate automatically on bugs linked to in changelog for
specific releases https://github.com/fedora-infra/bodhi/issue/4094
* Use the release git branch name to query PDC for critpath components
https://github.com/fedora-infra/bodhi/issue/4177
* Avoid using datetime.utcnow() for updateinfo <updated_date> and <issued_date>
elements, use "date_submitted" instead. https://github.com/fedora-infra/bodhi/issue/4189
* Updates which already had a comment that they can be pushed to stable were
not automatically pushed to stable when the stable_days threshold was
reached https://github.com/fedora-infra/bodhi/issue/4042

For further information, check out the Bodhi release notes:

https://github.com/fedora-infra/bodhi/releases/tag/5.7.0

cheers,

ryanlerch

_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure