- The Alembic configuration file has changed to use the Python path of the migrations.
In order to run the new migrations, you should ensure your alembic.ini has
script_location = bodhi:server/migrations.
- The client formally depends on
iniparsenow. It needed this before but the dependency was
- Bodhi no longer uses or requires
webhelpers. RSS feeds are now generated by
feedgen, a new
- Bodhi no longer uses or requires
- The CLI now prints a helpful hint about how to use
koji wait-repowhen creating or editing a
buildroot override, or when a query for overrides returns exactly one result (#1376).
- Bodhi now uses connection pooling when making API requests to other services (#1753).
- The bindings now conditionally import
- It is now possible to query for Releases by a list of primary keys, by using the querystring
- Builds now serialize their
- It is now possible to configure a maximum number of mash threads that Bodhi will run at once,
which is handy if the new Pungi masher has been mean to your NAS. There is a new
max_concurrent_mashessetting in production.ini, which defaults to
- There is now a man page for
- The documentation was reorganized by type of reader (14e81a8).
- The documentation now uses the Alabaster theme (f15351e).
- The CLI now has a
--archflag that can be used when downloading updates to specify which
architecture is desired (6538c9e).
- Bodhi’s documentation now includes an administration section which includes documentation
on its various settings (310f56d).
- Bodhi now uses the correct comment on critical path updates regarding how many days are required
in testing (#1361).
- All home page update types now have mouseover titles (#1620).
- e-mail subjects again include the version of the updates (#1635).
- The bindings will re-attempt authentication upon captcha failures (#1787).
- The formatting is fixed on mobile for the edit/create update form (#1791).
- The “Push to Stable” button is now rendered in the web UI on batched updates (#1907).
- Do not fail the mash if a changelog is malformed (#1989).
bodhi-dequeue-stableno longer dies if it encounters updates that can’t be pushed
- Unreachable RSS Accept-header based redirects were fixed (6f3db0c).
- Fixed an unsafe default in
- Bodhi now distinguishes between testing and stable when asking Greenwave for gating decisions
- The CLI now renders the correct URL for updates without aliases (:commit:
- The database migrations are now shipped as part of the Python distribution
- The developer docs pertaining to using virtualenvs have been corrected and improved
test_utils.pytests now use the
BaseTestCase, which allows them to pass when run by
- An obsolete mash check for symlinks was removed (:issue:
- A mock was moved inside of a test to avoid inter-test dependencies (:issue:
- Bodhi is now compliant with
- The JJB YAML file is now tested to ensure it is valid YAML (:#1934).
- Some code has been prepared for Python 3 compatibility (d776356).
- Developers are now required to sign the DCO (34d0ceb).
- There is now formal documentation on how to submit patches to Bodhi (bb20a0e).
- Bodhi is now tested by Fedora containers in the CentOS CI environment (36d603f).
- Bodhi is now tested against dependencies from PyPI (1e8fb65).
development.ini.examplefile has been reduced to a minimal form, which means we no longer
need to document the settings in two places (2b7dc4e).
- Bodhi now runs CI tests for different PRs in parallel (6427309).
Vagrantfile.examplehas been moved to
devel/for tidiness (21ff2e5).
- It is now easier to replicate the CI environment locally by using the
- Many more docblocks have been written across the codebase.
- Line test coverage is now at 93%.
The following developers contributed to Bodhi 3.1.0:
- Alena Volkova
- Aman Sharma
- Caleigh Runge-Hottman
- Dusty Mabe
- František Zatloukal
- Jeremy Cline
- Ken Dreyer
- Lumir Balhar
- Martin Curlej
- Patrick Uiterwijk
- Pierre-Yves Chibon
- Ralph Bean
- Ryan Lerch
- Randy Barlow