Last Friday, we officially released Pagure 5.3, the latest release in
the lightweight git-centered forge!
However, as we forgot to announce Pagure 5.2 last month, the total
changes between Pagure 5.1 and 5.3 are quite substantial. Note that
Pagure 5.3 includes the fix for CVE-2019-7628, which affects Pagure
5.2 deployments. If you're running older versions of Pagure, we
strongly urge you to upgrade to the latest version. We promise you'll
like it. :)
Without further ado...
Here are some of the highlights from Pagure 5.2:
* Add support for sending messages over the MQTT protocol
* Add support for mirroring in git repositories from outside sources
* Add support to merge a PR when the fork was deleted
* Add the ability to generate archive from a commit or tag
* Allow searching the content of the comments on an issue tracker
* Allow filtering the issue list by the close status
* Show related PRs on the issue list if there are any
* Add build status to pull requests page
* Add new API endpoints for get and set project options
* Add WIP/experimental/unstable support for third-party extensions to pagure
* Add support for rebasing pull-requests
* Implement a button to rerun CI tests on a pull request
* Support disallowing remote pull requests
* Add an about page in the themes
* Update the chameleon theme to the latest theme code release
And the highlights from Pagure 5.3:
* Add support for AMQP via the fedora-messaging Python module
* Improve filtering and searching through issues and PRs
* Add support for forcing highlight types based on file extensions
* Fix naming rules for labels/tags
* Fix support for repoSpanner Git storage backend
* Do not leak partial API keys in key expiration emails (resolves CVE-2019-7628)
These last two releases were made possible by 27 unique contributors,
with several first-time contributors! Congratulations to everyone, and
thank you for helping make Pagure better!
We're pleased to report that Pagure 5.3 is now available across a
number of Linux distributions:
* Fedora 30
* Fedora 29
* CentOS/RHEL 7 through EPEL
* Mageia 7
* openSUSE Tumbleweed
* openSUSE Leap 15.1
In all of these distributions, getting Pagure is just a matter of
installing the 'pagure' package and setting up from there. :)
Note that there may be distribution specific documentation shipped
with the package on how to set up, so check in the appropriate package
documentation location for your distribution for more information.
We hope to see Pagure packaged and shipped in more places and in more
ways. If you're interested in making Pagure available through another
distribution or operating system, or even a new deployment method, let
us know so we can let the world know! :)
Best regards and happy hacking!
真実はいつも一つ！/ Always, there's only one truth!
Good Morning Everyone,
I would like to announce that I will be delaying the 5.3 release of pagure.
I am currently reworking how we run the test suite so that we have the following
- Fedora 29, dependencies installed as RPMs, python 3
- CentOS 7, dependencies installed as RPMs, python 2
- Fedora 29, dependencies installed via pip, python 3
During this work, I encountered some bugs in pagure which I fixed as I saw them.
Some of these are related to the version of python-werkzeug shipped in
RHEL/CentOS (an old 0.9.1), upgrading this to at least 0.9.6 solves this. So if
you are using CentOS7 or RHEL7 you may want to see about doing this(bug report
to RHEL https://bugzilla.redhat.com/show_bug.cgi?id=1672360)
At this time, I hope/expect to cut the beta release next Monday, and the release
probably the week after that if everything goes smoothly.
Sorry for the late notice,