Releases: fedora-infra/bodhi
25.11.2
Released on 2025-11-23.
This is a bugfix release.
Bug fixes
- When expiring an override don't require candidate or testing build tags (#5937).
- bodhi-server: refine logic to avoid stuck side-tag updates for releases not composed by bodhi (#5989).
- bodhi-server: skip updating the gating status if the current status is 'waiting', and the message we're handling is for a QUEUED or RUNNING result (#6000).
- bodhi-server: gating status should be correctly updated to 'waiting' when all failed tests on an update are restarted. (#6001).
Other changes
- server: usage of
os.scandir()instead ofos.listdir()in clean_old_composes task should give better performance (#5999).
Contributors
The following developers contributed to this release of Bodhi:
- Adam Williamson
- Mattia Verga
25.11.1
Released on 2025-11-01.
This release fixes a few bugs regarding the display of automated test results
in web pages.
Dependency changes
- bodhi-server: dependency on waitress now requires a version greater than
3.0.1 (#5897). - bodhi-server: support for configuring logging through pyramid_sawing has been
removed (#5906).
Features
- User statistics in homepage will now default to show 10 entries. This number
can be configured in Bodhi's config file. (#5882).
Bug fixes
- client: aliases for Fedora Flatpak updates are now recognized from command
line (#5918). - Fixed a schema issue which prevented to set the
released_onproperty on
Release (#5964).
Contributors
The following developers contributed to this release of Bodhi:
- Akashdeep Dhar
- Adam Williamson
- Jens Petersen
- Mattia Verga
- Yaakov Selkowitz
25.5.1
Released on 2025-05-17.
This adds a couple of features that were not included in the previous release by mistake.
Features
- The CLI updates download command will now download signed packages, if possible. (#5859).
Bug fixes
UpdateType.unspecifiedthat was introduced with PR#3047 has been added to the documentation andconstants.UPDATE_TYPESlist. (#5892).
Contributors
The following developers contributed to this release of Bodhi:
- Adam Williamson
- LuK1337
25.5.0
Released on 2025-05-16.
This is mostly a bugfix release, see the following notes for a detailed
description.
Features
- bodhi-server: Updates which fail gating tests are now marked by an icon in the update list view (#5852).
Bug fixes
- When creating a new Update, do not add relationships before the Update object is in session. Fixes some SQLAlchemy 2.x warnings. (#5840).
- The task responsible for unstuck updates ejected from the push has been fixed for correct handling side-tag updates (#5850).
- The Automated Tests tab now correctly indicates when a required test failure was waived if the test case has no 'scenario'. (#5863).
- Where available, libdnf5 Python bindings are now used in repository sanity checks, otherwise we're forcing dnf-4 usage with the old method (#5820).
- Builds for rawhide or branched updates are now moved from pending-testing to testing tag when the update is moved into testing. Despite being pointless, this ensure to not break update flow when a release enters Bodhi activation point (#5830).
Contributors
The following developers contributed to this release of Bodhi:
- Akashdeep Dhar
- Aurélien Bompard
- Adam Williamson
- Peter Oliver
- Mattia Verga
8.3.0
Released on 2024-11-25.
This is a feature release that re-adds the distinction between min_karma and critpath.min_karma settings.
Features
- Bodhi now allows setting the min_karma threshold for critical path and non-critical path updates separately (#5802).
- bcd has a new clean subcommand to completely refresh the bcd environment (#5804).
- WebUI: the update page now reports both the autopush settings and the minimum threshold for the manual push (#5805).
- The Release properties
min_karma,critpath_min_karma,mandatory_days_in_testingandcritpath_mandatory_days_in_testingare now expossed in JSON replies from bodhi-server and can be viewed in bodhi-client through therelease requirementscommand (#5807).
Bug fixes
- Bodhi documentation on RTD was missing some content generated by external scripts (#5789).
- When editing an update from APIs it is no more required to specify the old bug ids list in sent data if no change is required (#5800).
Development improvements
- A deprecation warning is now emitted when a value for
karma_critpathis set in a comment (#5796).
Contributors
The following developers contributed to this release of Bodhi:
- Adam Williamson
- Mattia Verga
8.2.0
Released on 2024-10-26.
This is a feature release that needs configuration file adjustments. See the following notes for the details.
Backwards incompatible changes
-
Bodhi's update status checking has been overhauled, and some configuration options have changed.
critpath.num_admin_approvalsis removed. This backed the old Fedora "proventesters" concept, which has not been used for some years.critpath.min_karmais removed and is replaced by a new setting just calledmin_karma. This applies to all updates, not just critical path.critpath.stable_after_days_without_negative_karmais renamed tocritpath.mandatory_days_in_testingand its behavior has changed: there is no longer any check for 'no negative karma'. Critical path updates, like non-critical path updates, can now be manually pushed stable after reaching this time threshold even if they have negative karma.
As before, these settings can be specified with prefixes to apply only to particular releases and milestones.
min_karmaand(critpath.)mandatory_days_in_testingnow act strictly and consistently as minimum requirements for stable push. Any update may be pushed stable once it reaches either of those thresholds (and passes gating requirements, if gating is enabled). The update'sstable_karmavalue is no longer ever considered in determining whether it may be pushed stable.stable_karmaandstable_daysare only used as triggers for automatic stable pushes (but for an update to be automatically pushed it must also reach eithermin_karmaor(critpath.)mandatory_days_in_testing).The most obvious practical result of this change for Fedora is that, during phases where the policy minimum karma requirement is +2, you will no longer be able to make non-critical path updates pushable with +1 karma by setting this as their
stable_karmavalue. Additionally:- It is no longer possible to set an update's request to 'stable' if it has previously met requirements but currently does not
- Two cases where updates that reached their unstable_karma thresholds were not obsoleted are resolved
- Updates in 'pending' as well as 'testing' status have autopush disabled upon receiving any negative karma
- The
date_approvedproperty of updates is more consistently set as the date the update first became eligible for stable push (#5630).
Features
- When searching updates, you can now specify multiple gating statuses by passing the 'gating' query arg more than once (#5658).
- Bundled fedora-bootstrap has been updated to 5.3.3-0 (#5711).
- A packager can now edit a side-tag update even if the side-tag is not owned by them, provided they have commit rights on all packages included in the side-tag (#5764).
Bug fixes
- The development.ini.example config - on which the BCD config is based - is now set up to listen on both IPv4 and IPv6 (#5659).
- Openid based login support has been removed from Bodhi.
python-openidandpyramid-fas-openidare EOL and we moved to OIDC authentication. (#5601). - Fixed a build validation issue which would prevent a sidetag update from being submitted in some circumstances (#5725).
- Fixed broken pagination for listing updates in webUI and JSON (#5738).
Development improvements
- Calls to
datetime.datetime.utcnow()have been changed todatetime.datetime.now(datetime.timezone.utc). We previously assumed all datetimes were UTC based, now this is explicit by using timezone aware datetimes (#5702).
Documentation improvements
- Bodhi's documentation is now served from ReadTheDocs pages (#5774).
Contributors
The following developers contributed to this release of Bodhi:
- Adam Williamson
- Mattia Verga
- Nikola Forró
- Ryan Lerch
8.1.1
Released on 2024-06-22.
This is a bugfix release, see below for the details.
Bug fixes
- Builds passed alongside a side-tag in update forms were not validated correctly against the side-tag (#5647).
- build with spec false: build require python3dist(poetry-core) >= 1 but not in spec BuildRequires (#5678).
- bodhi server web Incorrect static resource path for httpd, always "python3.7" python3_version in /etc/httpd/conf.d/bodhi.conf, fix in bodhi-server.spec (#5680).
- Fixed the release list web page which was not updated after a release changed state (#5684).
- Fixed bodhi-server enums initialization in Python 3.13 (#5685).
Contributors
The following developers contributed to this release of Bodhi:
- niuwanli
- Mattia Verga
8.1.0
Released on 2024-04-09.
This is a feature release that adds options for running createrepo_c.
Features
- Bodhi can now set a timeout on postgresql database queries (default to 30 sec) (#5593).
- The createrepo_c config file now can accept enabling/disabling sqlite metadata generation and using --compatibility flag (#5617).
- Builds submission can now be restricted to only specified sources (#5556).
- A new
/list_releases/GET endpoint is available to allow retrieving JSON data through ajax calls. (#5587).
Bug fixes
- Use urljoin for update URLs construction (#5566`).
- DRPMs can now be disabled per Release in createrepo_c config file (#5616).
Development improvements
- The Vagrant development environment is entirely removed in favor of BCD, and bodhi-shell is fixed in BCD. (#5600).
Contributors
The following developers contributed to this release of Bodhi:
- Aurélien Bompard
- Adam Williamson
- Mattia Verga
bodhi-server 8.0.2
Released on 2024-01-11.
This is a bugfix release.
Bug fixes
- Fixed Automated Tests table in the web UI not showing missing results or remote rule errors correctly (#5581).
Contributors
The following developers contributed to this release of Bodhi:
- Adam Williamson
bodhi-server 8.0.1
Released on 2023-12-24.
This is a bugfix release that fixes an urgent issue about bodhi-server not honouring cookie authentication settings.
Bug fixes
- The Bodhi authentication policy wasn't honoring settings from config (#5572).
Contributors
The following developers contributed to this release of Bodhi:
- Mattia Verga