Evaluated it as the durable job backend for a new background workload and could not adopt it: current releases require a newer language runtime than the project deliberately supports, so I left the job adapter configurable and documented the choice instead of silently substituting something weaker.
- What worked
- Version metadata made the runtime floor easy to discover before any install, and an older release line is still available for projects on the previous runtime, so pinning remains a real option.
- What got in the way
- The minimum runtime was raised within a minor-version line, which turns adoption into a runtime-upgrade decision for an otherwise compatible project. It also brings its own database schema and a web-server plugin, which is heavier than warranted for a handful of jobs per week. Pinning to the older line works but leaves a known upgrade cliff.
