Good Morning Everyone, On Monday, I released a new version of pagure: 5.0. Here is its changelog: 5.0 (2018-09-24) ---------------- .. warning:: This release contains backward incompatible changes and fixes a CVE - Pagure supports now python2 and python3 simultaneously (Thanks to Aurélien Bompard and Neal Gompa for the testing) - New UI deployed (thanks to Ryan Lerch) - New dashboard page as index page when authenticated (Ryan Lerch) - API listing items (projects, issues, pull-requests are now paginated ( Karsten Hopp) .. warning:: Backward incompatible - Enable private projects by default (Neal Gompa) .. warning:: Backward incompatible - Change the default and sample configuration to point to localhost-friendly resources (Neal Gompa) .. warning:: Backward incompatible - Disable sending FedMsg notifications by default (Neal Gompa) .. warning:: Backward incompatible - Switch default authentication to `local` (Neal Gompa) .. warning:: Backward incompatible - Drop the dependency on python-pygments - Drop the dependency on flask-multistatic - Drop the dependency on python-trollius (in favor of python-trololio) (Neal Gompa) - Bump pygit2 requirement to 0.24.0 minimum .. warning:: Backward incompatible - Add support to re-open a pull-request (Karsten Hopp) - Fix editing a file into a fork containing a namespace - Allow creating a new API token based on an expired one - New API endpoint to submit a pull-request - Add support for making the issue tracker read-only - Add a new API endpoint allowing to update watch status on a project - Paginate the project lists on the front pages - Let the reply button append instead of replacing - Add a way to list all API tokens and don't restrict the info command ( in pagure-admin) - Expand pagure-admin to allow using it to block an user - Expand pagure-admin to allow adding new groups using it - Allow viewing commits from a git tag - Support viewing commits from a specific commit hash - Add a hook that disables creating new branches by git push (Slavek Kabrda) - Make API endpoint for creating new git branch have its own ACL - Support sorting PR's by recent activity (ymdatta) - Fix installing the API key reminder cron with systemd integration - Add reactions to comments (Lubomír Sedlář) - New API endpoint allowing to retrieve pull-requests based on their UUID (Slavek Kabrda) - Add an option to restrict emails sent to certain domains (Karsten Hopp) - Integration with repospanner (Patrick Uiterwijk) - Rework how git hooks work to rely on a single file rather than moving files around (Patrick Uiterwijk) - Add themes for pagure.io, src.fedoraproject.org (Ryan Lerch) - Add themes for OpenSUSE (hellcp) - Ensure remote PR are opened from a remote URL (CVE-2018-1002158 - reported by Patrick Uiterwijk) This release is available: - In Fedora - In Mageia - In OpenSUSE - soon in EPEL This release has been deployed in staging: stg.pagure.io and src.stg.fedoraproject.org and in production in pagure.io yesterday. We ran into some interesting issues in production that we didn't see in staging, leading to some bug fixes and a version 5.0.1 to be released soon. I take this opportunity to advertise that pagure now has two mailing lists: - pagure-devel to discuss about the development of pagure: https://lists.pagure.io/admin/lists/pagure-devel.lists.pagure.io/ - pagure-announce to follow announcement about new releases of pagure https://lists.pagure.io/admin/lists/pagure-announce.lists.pagure.io/ feel free to join them and keep in touch with pagure :) Future pagure release announcement will be sent to: pagure-announce@xxxxxxxxxxxxxxx Happy hacking! Pierre
Attachment:
pgpPxXN_RHQhk.pgp
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
