mr.zero 763a092640 warp_engine: load ActiveJob itself so production eager load works ...

The engine ships an ActiveJob based job (PipelineSyncJob), but a host's
application.rb does not necessarily require active_job/railtie - apps/api does
not. With eager loading off (development, test) nothing noticed; in production
WarpEngine::ApplicationJob blew up with "uninitialized constant
WarpEngine::ActiveJob", which is exactly what `rails zeitwerk:check` in
RAILS_ENV=production reported. An engine that ships jobs has to pull in the
framework it needs, so lib/warp_engine.rb requires the railtie.

Pre-existing on 0.1.0 as well; found while verifying that the 0.2.0 changes do
not break the portal. All three api-test steps are green now.

apps/api Gemfile.lock follows the 0.1.0 -> 0.2.0 path gem bump.

2026-08-10 11:30:06 +02:00

..

api

warp_engine: load ActiveJob itself so production eager load works

2026-08-10 11:30:06 +02:00

frontend

package upgrades

2026-08-09 17:57:08 +02:00