⬆️ Bump solid_queue from 1.5.1 to 1.6.0

[dependabot]

Bumps solid_queue from 1.5.1 to 1.6.0.

Release notes

Sourced from solid_queue's releases.

v1.6.0 - fiber execution mode (with Async)

A long-awaited feature thanks to @​crmne on this release: instead of using a thread pool to run jobs in multiple threads per works, you can now use fibers on a single fiber reactor thread. To use this, you just need to specify the number of fibers instead of the number of threads in your worker configuration, like this:

workers:
  - queues: "api*"
    fibers: 100
    polling_interval: 0.05

It uses Async under the hood, so you need to have that as a dependency for it to work. Also, you need to be using fiber isolation in Rails (config.active_support.isolation_level`` = :fiber).

This can be very useful for I/O-bound workloads, such as those involving LLM calls.

What's Changed

• Add fiber worker execution mode by @​crmne in rails/solid_queue#728
• Roll back transactions leaked by killed job threads in tests by @​rosa in rails/solid_queue#773
• Document how to update dynamic recurring tasks by @​wintan1418 in rails/solid_queue#777

New Contributors

• @​crmne made their first contribution in rails/solid_queue#728
• @​wintan1418 made their first contribution in rails/solid_queue#777

Full Changelog: rails/solid_queue@v1.5.1...v1.6.0

Commits

• 86f3d92 Bump solid_queue to 1.6.0
• 2a479f6 Document how to update dynamic recurring tasks
• 7f59932 Roll back transactions leaked by killed job threads in tests
• 9c0d5d3 Reorganize the execution pools under SolidQueue::Pool
• 30b92ca Move the fiber worker checks to Configuration
• 6e27144 Extract a base class for the execution pools
• 08e6098 Rescue only the code that runs with capacity reserved when posting
• 000e8ba Report errors escaping the execution future
• 5270cc8 Simplify worker initialization
• 50468fa Start the fiber pool's reactor lazily on first use
• Additional commits viewable in compare view

---

Note

Medium Risk
Bumps the background job backend with internal execution-pool changes; default thread mode is unchanged, but job processing is infrastructure-critical so regression testing of workers and recurring jobs is worthwhile.

Overview
Updates only Gemfile.lock: solid_queue 1.5.1 → 1.6.0, plus transitive bumps (et-orbi, rbs, zeitwerk). No application or worker config changes.

solid_queue 1.6.0 adds optional fiber-based job execution (Async + fibers in worker YAML) and refactors execution pools; this app still runs the usual thread workers via solid_queue:start / active_job.queue_adapter = :solid_queue, so behavior should match 1.5.1 unless you adopt fiber workers later.

^{Reviewed by Cursor Bugbot for commit 6e1f1ea. Bugbot is set up for automated code reviews on this repo. Configure here.}