Meeting Type: Foreman Release Team Meeting
Date: April 15, 2026
Community: https://community.theforeman.org
Foreman Nightly
- The plugins pipeline is failing on repoclosure with
unresolved deps: (foreman-opentofu-selinux if selinux-policy-targeted) - foreman-staging-repoclosure-el9 failing on repoclosure too:
unresolved deps: npm(diff) = 5.2.0- @Zhunting raised a fix for it https://github.com/theforeman/foreman-packaging/pull/13358
- hammer jobs failed with “No test results found”. We’ll retrigger them to see if it is transient. Otherwise, we’ll file a fix.
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
- 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] Pulp 105 needs a bunch of new packages for pulp-python
- [Quinn] The 3.105 upgrade is going well but we’ll need a one line change to pulp-python to allow for smart proxy repository sync when not using publications.
- We expect backports to pulp-container due to postquantum crypto support
- It’s Rust. We need to vendor stuff
- We can’t merge changes to pulp-container to 3.85 atm, we’re waiting for 3.105 branching
- Katello 4.21 to be updated to pulpcore 3.105
- We’ll need a new Postgres with 3.105 because of Django 5
- We confirmed with Candlepin - Candlepin should work with the new Postgres
- We need to test whether migrations work as expected
- We’ll need a new Postgres with 3.105 because of Django 5