Meeting Type: Foreman Release Team Meeting
Date: April 22, 2026
Community: https://community.theforeman.org
Foreman Nightly
- Next week is Foreman 3.19 prep week
- smart-proxy jobs are failing due to the new Rake version that broke the ci_reporter
- smart-proxy should be migrated from test-unit to minitest to align with Foreman core. That means migrating from ci_reporter to minitest-reporters.
- This has been discussed in #theforeman-dev channel between @evgeni and @ekohl
- Bug #39248: smart-proxy test failures due to rake 13.4.2 breaking ci_reporter_test_unit - Smart Proxy - Foreman has been created to track this
Foreman 3.18
- Status Updates
- CI is green
- We expect a release in April. Exact date to be posted in the Release Procedure.
Foreman 3.17
- Current Release Status
- CI is green
- We expect a release in April. Exact date to be posted in the Release Procedure.
Katello 4.20
- Status Updates
- No releases planned at the moment. We may release 4.20.1 soon
- Katello folks would like to handle (small) Katello releases within a given X.Y series - Z-streams.
- Release engineers to make sure we have up-to-date procedures in the foreman-rel-eng to reduce ambiguity.
- Katello folks can start anytime they want
Pulp Integration
- Current Status
- [Odilon] Branching 3.105 is done, RPMs are done, we added 11 new packages
- Katello 4.21 to be updated to pulpcore 3.105
- [Quinn] The 3.105 upgrade is going well. 3/4 of the work is in review
- Nightly might be broken until we update Pulp bindings
- We’ll need Postgres 16 with 3.105 because of Django 5; we’re still on Django 4
- There’s Support PostgreSQL 16 · Issue #465 · theforeman/foremanctl · GitHub at the moment to track this work.
- We confirmed with Candlepin - Candlepin should work with the new Postgres
- We need to test whether migrations work as expected