1. Headline features

1.1. User interface & experience

Foreman recurring tasks use standardized rake tasks and systemd timers

In this release, recurring Foreman maintenance tasks are no longer managed by ad‑hoc cron jobs. Instead, they now run through a standardized set of rake tasks, managed in /etc/cron.d/foreman. This change provides a more container‑native approach and enables plugins to register their tasks by using the Foreman::Cron framework.

Foreman core provides the following rake tasks:

  • foreman-rake cron:hourly

  • foreman-rake cron:daily

  • foreman-rake cron:weekly

  • foreman-rake cron:monthly

Users can no longer freely customize arbitrary schedules for these core recurring jobs. This is an intentional limitation to keep behavior more predictable and maintainable.

Important

During upgrade, existing cron schedules are not automatically detected or preserved. After upgrading, recurring jobs run on the new standardized schedules. If you previously relied on custom timings, review the new behavior and adjust any custom automation.

1.2. Infrastructure & platform updates

1.3. Networking & connectivity

1.4. Clients

1.5. Documentation & tooling

2. Upgrade warnings

There are no upgrade warnings with Foreman nightly.

3. Deprecations

Hammer CLI plugin Admin is deprecated

As an alternative, you can use the foreman-installer to manage your Foreman server or Smart Proxy server.

Appendix A: Foreman contributors

Pre-release version Report issue