diff options
| author | talyz <kim.lindberger@gmail.com> | 2021-12-02 11:55:07 +0100 |
|---|---|---|
| committer | talyz <kim.lindberger@gmail.com> | 2021-12-02 11:55:07 +0100 |
| commit | 4fb343c87e29bf1f33b49a1bcc210a57d9d42f1d (patch) | |
| tree | d6c2c6a0cf7d2b044ecf090d93d082a67b0d7756 /pkgs/development/python-modules/cppheaderparser | |
| parent | ab042d6452751e9d6e7c222e5fcb194e3d3c0ba9 (diff) | |
discourse: update.py: Improve version handling, use pinned plugins
Add a DiscourseVersion class which handles Discourse's version
numbering properly when sorting - beta versions are sorted lower than
their respective release versions. It can also return both its version
number and equivalent git tag, removing the need for `rev2version` and
manually adding `v` to the front.
Using DiscourseVersion instead of LooseVersion, we can list all
current version number tags from the `discourse` repo and sort them
correctly, giving us the latest one, regardless of type; i.e. we don't
have to filter for only release versions or beta versions anymore.
This also implements the plugin pinning algorithm laid out here:
https://meta.discourse.org/t/pinning-plugin-and-theme-versions-for-older-discourse-installs/156971
to make sure we don't upgrade plugins further than what's compatible
with our currently packaged Discourse version. While it likely won't
matter much most of the time if we continue packaging the beta
versions, it could be helpful if we decide to go back to packaging
release versions or if we run into issues with future upgrades. In
that case, the plugins could still be updated safely even though we're
not on the latest version of Discourse.
Diffstat (limited to 'pkgs/development/python-modules/cppheaderparser')
0 files changed, 0 insertions, 0 deletions
