Skip to content

Bump the production-dependencies group across 1 directory with 6 updates - #391

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/production-dependencies-76dd47e67c
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/production-dependencies-76dd47e67c

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 18, 2026

Copy link
Copy Markdown

Bumps the production-dependencies group with 6 updates in the / directory:

Package From To
puma 8.0.2 8.1.0
solid_queue 1.7.0 1.7.2
bootsnap 1.26.0 1.26.1
thruster 0.1.26 0.1.27
ruby_llm 2.1.0 2.2.2
ruby_llm-schema 0.4.0 1.0.0

Updates puma from 8.0.2 to 8.1.0

Release notes

Sourced from puma's releases.

v8.1.0 - Puma Psychosis

  • Features

    • Add experimental mold_worker cluster mode, an alternative to fork_worker where new workers are forked from a retired worker that no longer serves traffic (#4038, #4044, #4055)
    • Add on_worker_boot hooks and hook_error_handler (#3982)
    • Add Puma::Client.connection_closed? API (#4019)
    • Add continue_callback to answer Expect: 100-continue before the request body is read (#4028)
    • Send a systemd watchdog ping immediately on ready (#3980)
    • Support the HTTP QUERY method (#3973)
    • Allow a sub-second worker_check_interval (#3964)
    • Add allow_underscore_headers option; set it to false to discard request headers with underscores in their names (#3937)
  • Security (Hardening)

    • Limit the size of a chunked request trailer section (#4059)
    • Reject unescaped {, }, ` and \ in the request path (#3976)
    • Reject Content_Length and Transfer_Encoding framing headers regardless of allow_underscore_headers (#4021)
    • Clear the SSL key password callback after loading the private key (#4027)
    • Respond with 400 to HTTP/1.1 requests with a missing or empty Host header (#3957)
    • Reject empty chunk sizes (#3952)
  • Bugfixes

    • Fix IO#close hang when notify_safely runs in a signal handler (#4098)
    • Fix fork_worker refork recovery (#4056)
    • Keep a socket-activated control URL for the control server (#4037)
    • Close path-backed response files when writing fails (#4033)
    • Don't send content-length: 0 on 304 responses with an empty body (#4036)
    • Fix accepting one more request after the worker shutdown command is sent (#4032)
    • Honour the close option when it appears in a Connection header list (#4031)
    • Fix wakeup deadlock (#4025)
    • Fix NoMethodError when a malformed request has no request line (#3992)
    • Require null_io in client.rb so puma/client loads on its own (#4024)
    • Avoid keep-alive requeue into a shutting-down thread pool (#4016)
    • Fix CommonLogger nil-logger fallback to rack.errors (#4023)
    • Fix chunked body parsing when the last-chunk terminator arrives split (#3970)
    • Run after_stopped hooks after request draining (#4001)
    • Restore admission gate when queue_requests is disabled (#3969)
    • Fix pool_capacity leak when extra IO threads exit (#3968)
    • Fix worker shutdown hang in notify_safely (#3940)
    • Defer removal of on_booted, on_restart and on_stopped to Puma 9 (#3938)
    • Fix Configuration#clamp being called twice in Launcher (#3939)
  • Docs

    • Add an initial Puma support document (#3700)
    • Document the bundled sd_notify license in the README (#4102)
    • Add a threat model to SECURITY.md (#4064)
    • Fix typos and grammar in README, CONTRIBUTING and docs (#4035, #3974)
    • Improve DSL documentation, including queue_requests (#3966, #3965)

v8.0.4

... (truncated)

Changelog

Sourced from puma's changelog.

8.1.0 / 2026-11-15

  • Features

    • Add experimental mold_worker cluster mode, an alternative to fork_worker where new workers are forked from a retired worker that no longer serves traffic (#4038, #4044, #4055)
    • Add on_worker_boot hooks and hook_error_handler (#3982)
    • Add Puma::Client.connection_closed? API (#4019)
    • Add continue_callback to answer Expect: 100-continue before the request body is read (#4028)
    • Send a systemd watchdog ping immediately on ready (#3980)
    • Support the HTTP QUERY method (#3973)
    • Allow a sub-second worker_check_interval (#3964)
    • Add allow_underscore_headers option; set it to false to discard request headers with underscores in their names (#3937)
  • Security (Hardening)

    • Limit the size of a chunked request trailer section (#4059)
    • Reject unescaped {, }, ` and \ in the request path (#3976)
    • Reject Content_Length and Transfer_Encoding framing headers regardless of allow_underscore_headers (#4021)
    • Clear the SSL key password callback after loading the private key (#4027)
    • Respond with 400 to HTTP/1.1 requests with a missing or empty Host header (#3957)
    • Reject empty chunk sizes (#3952)
  • Bugfixes

    • Fix IO#close hang when notify_safely runs in a signal handler (#4098)
    • Fix fork_worker refork recovery (#4056)
    • Keep a socket-activated control URL for the control server (#4037)
    • Close path-backed response files when writing fails (#4033)
    • Don't send content-length: 0 on 304 responses with an empty body (#4036)
    • Fix accepting one more request after the worker shutdown command is sent (#4032)
    • Honour the close option when it appears in a Connection header list (#4031)
    • Fix wakeup deadlock (#4025)
    • Fix NoMethodError when a malformed request has no request line (#3992)
    • Require null_io in client.rb so puma/client loads on its own (#4024)
    • Avoid keep-alive requeue into a shutting-down thread pool (#4016)
    • Fix CommonLogger nil-logger fallback to rack.errors (#4023)
    • Fix chunked body parsing when the last-chunk terminator arrives split (#3970)
    • Run after_stopped hooks after request draining (#4001)
    • Restore admission gate when queue_requests is disabled (#3969)
    • Fix pool_capacity leak when extra IO threads exit (#3968)
    • Fix worker shutdown hang in notify_safely (#3940)
    • Defer removal of on_booted, on_restart and on_stopped to Puma 9 (#3938)
    • Fix Configuration#clamp being called twice in Launcher (#3939)
  • Docs

    • Add an initial Puma support document (#3700)
    • Document the bundled sd_notify license in the README (#4102)
    • Add a threat model to SECURITY.md (#4064)
    • Fix typos and grammar in README, CONTRIBUTING and docs (#4035, #3974)
    • Improve DSL documentation, including queue_requests (#3966, #3965)

8.0.4 / 2026-11-17

... (truncated)

Commits
  • df5dc1a Release v8.1.0 (#4111)
  • 193d3a0 CI: skip Ragel install in tests, skip draft PRs, inline duplicate-run check, ...
  • 4bf39aa Reduce CI queue time: slim PR matrix, run rubocop in parallel, drop release-v...
  • 507d52f Define Puma's SemVer public API and Security (Hardening) History group [ci sk...
  • 38bc618 Remove unused devcontainer config [ci skip] (#4115)
  • 30ef014 Sync 8.0.3 version to main; cover version in release skill main sync (#4112)
  • 124ce1e Add a security triage skill for agents [ci skip] (#4110)
  • 9f7541e Add releasing-puma agent skill (#4107)
  • f32e55d Merge security fixes from 8.0.3 and 7.2.2 into main (#4103)
  • 239a72b Document bundled sd_notify license in README [ci skip] (#4102)
  • Additional commits viewable in compare view

Updates solid_queue from 1.7.0 to 1.7.2

Release notes

Sourced from solid_queue's releases.

v1.7.2

Summary

Concurrency-limited jobs now give their slot back only to the semaphore they got it from. That fixes a job that ran past its duration letting an extra job run alongside the next holder (#827). It also fixes jobs whose class goes missing during a deploy giving back a slot they never took, or keeping one they did take. Nothing needs migrating; see "Upgrading to version 1.7.2" for what to do before 2.0.

What's Changed

Full Changelog: rails/solid_queue@v1.7.1...v1.7.2

v1.7.1

Summary of changes

Process resilience

  • Processes stop and get replaced when their heartbeats keep failing past the alive threshold (#778).
  • The async supervisor replaces dead threads even if releasing their jobs fails during a database outage (#791, fixes #823).
  • Workers stop when finishing a job fails (#768).
  • Forked processes exit immediately, which avoids the exit hang on SQLite (#801).
  • The Puma plugin keeps shutting down when its output pipe is gone (#800, #737).
  • In async mode, in-flight jobs go back to the queue when shutdown times out (#815).

Jobs and concurrency

  • Jobs whose class no longer loads are failed with ClassMissingError instead of being dropped (#783).
  • Discarding ready jobs in bulk unblocks the jobs waiting behind them (#818).
  • Retrying failed jobs in bulk resets their retry counters (#817).
  • Concurrency locks are taken in key order when dispatching several jobs, which avoids deadlocks (#812).
  • One less query per enqueue (#819).
  • On MySQL, failed jobs with very large error messages no longer crash workers (#822).
  • Bulk-discarding claimed executions raises UndiscardableError instead of NameError (#828).
  • Batch completion errors no longer block the next job (#816).

Queues and recurring tasks

  • Queue prefixes escape _ and %, and each queue is selected only once (#811).
  • Dynamic tasks recreated with the same key are rescheduled (#793).

Other

  • The CLI is no longer eager loaded (#826).
  • CI pins json below 3 for Rails 7.1 and 8.0 (#813). That's test-only, but it explains the Gemfile change.
  • README additions: READ COMMITTED for MySQL, sql_notifications, the Puma plugin's behavior, retry_on and process death, async mode with TERM and QUIT, and removing leftover recurring tasks.

What's Changed

... (truncated)

Commits
  • b9c646a Bump solid_queue to 1.7.2
  • 8b2a87b Let the job answer for the concurrency slot it holds
  • 310496a Test that a job records the semaphore it created on MySQL, and correct the up...
  • 6af5101 Place the semaphore note under 1.7.2 in UPGRADING
  • 50ca656 Read the acquired semaphore with a lock, and record the limit used
  • 62c2927 Give concurrency slots back only to the semaphore they came from
  • 24d936a Bump solid_queue to 1.7.1
  • 3d7c5d0 Keep batch completion errors from blocking subsequent jobs
  • 7323f03 Move the concurrent dispatching test next to the other semaphore lock tests
  • a034856 Acquire concurrency locks by key when dispatching several jobs
  • Additional commits viewable in compare view

Updates bootsnap from 1.26.0 to 1.26.1

Changelog

Sourced from bootsnap's changelog.

1.26.1

  • Fix Bootsnap.enable_frozen_string_literal(app_only: true) raising NameError when the compile cache is disabled. App files are now compiled with frozen string literals on every load, without caching.

  • Avoid transcoding Ruby source when the Prism workaround runs with a default internal encoding.

  • Better detect support for fast path scanning. Fix compilation on Illumos.

Commits
  • 681429d Release 1.26.1
  • 9298a58 Merge pull request #582 from byroot/compiler-no-cache
  • e340dd0 Support custom compilers even whith caching disabled
  • 82b9598 Merge pull request #578 from byroot/windows-binmode
  • 8ad8d73 Read and write loadpath cache in binmode
  • dd767a4 Merge pull request #581 from czj/ci-old-rubies-on-ubuntu-24.04
  • a53f3de CI: run Ruby < 3.2 on ubuntu-24.04 now that ubuntu-latest is 26.04
  • db216d1 Merge pull request #576 from pauljccode/fix/source-internal-encoding
  • d53eb60 Declare the UTF-8 regression fixture encoding
  • d5cdf8a Preserve source encoding in the Prism workaround
  • Additional commits viewable in compare view

Updates thruster from 0.1.26 to 0.1.27

Changelog

Sourced from thruster's changelog.

v0.1.27 / 2026-09-28

  • Update dependencies (#154)
  • Bump golang.org/x/crypto to v0.56.0 (#152)
  • Build with Go 1.27.1, update dependencies, add make check (#150)
Commits
  • 669643f Merge commit from fork
  • 38d3721 Merge pull request #155 from erikthoreson24/version-0.1.27
  • 0992970 Bump version
  • 72796d7 Merge pull request #154 from basecamp/deps
  • 0864e8a Use http.Transport for h2c test client
  • 80e89ee Update dependencies
  • 22a9978 Merge pull request #152 from erikthoreson24/fix/bump-x-crypto-0.56.0
  • b186518 Bump golang.org/x/crypto to v0.56.0
  • 3ef8516 Merge pull request #150 from basecamp/go-1.27.1
  • fa31b96 Add make check to run go vet and govulncheck
  • Additional commits viewable in compare view

Updates ruby_llm from 2.1.0 to 2.2.2

Release notes

Sourced from ruby_llm's releases.

RubyLLM 2.2.2 loads the Ruby classes apps keep in app/skills again, keeps model rows your chats still use when a registry refresh runs without a foreign key, and shows each choice's title on the generated question cards.

bundle add ruby_llm --version 2.2.2

Already on 2.2? Run bundle update ruby_llm. No schema or code changes are needed.

Fixed

  • Your own classes in app/skills load again. 2.2 told the Rails autoloader to skip the whole app/skills folder, so an app that keeps its own Ruby classes there got NameError for every one of them after upgrading, whether or not it used RubyLLM skills. Now only skill folders are skipped: any folder holding a SKILL.md, at any depth, including skill folders that are symbolic links. Everything else in app/skills loads as it did in 2.1, and a skill you add while the development server runs is skipped on the next reload, with no restart. By @​crmne; thanks @​sebscholl. (#1671, #1675)
  • A model refresh keeps the models your chats use, with or without a foreign key. Refreshing the model registry deleted ruby_llm_models rows it no longer listed, and only the foreign key from chats stopped it from deleting rows a chat still pointed at. Schemas without that key, such as MySQL setups that skip foreign keys, lost those rows and left chats pointing at nothing. Referenced rows are now kept and marked unlisted, as they are with the foreign key. By @​yshmarov. (#1670)

New

  • Question cards show each choice's title. When a tool's ask or an MCP server gives its choices titles, the generated chat UI showed the raw values, such as 17 and 42, instead of "River bank" and "Money bank". The cards now label each button and option with its title and still submit the value. Your own UI can read the titles with field.choice_titles, which understands oneOf and items.anyOf with const and title, and enumNames. Regenerate the chat UI to pick it up. By @​kryzhovnik. (#1661)

Thanks

Thanks to @​yshmarov and @​kryzhovnik for the fixes in this release, and to @​sebscholl for reporting the app/skills regression.

Full changelog: crmne/ruby_llm@v2.2.1...v2.2.2

RubyLLM 2.2.1 caps how many tool calls one answer may run, keeps a tool that already acted from running twice when another raises, fixes a deadlock Postgres apps could hit while a reply saved, and fixes Gemini batches, judgments, file stores and the generated question cards.

bundle add ruby_llm --version 2.2.1

Already on 2.2? Run bundle update ruby_llm. No schema or code changes are needed.

New

  • Cap the tool calls one answer may run. A model can ask for hundreds of tool calls in a single response. with_tool_options(calls: 50) runs the first 50; the rest get an error telling the model to continue a few calls at a time, so they never run and never ask for approval. Set it on an agent with tool_options rounds: 25, calls: 50, and watch it with the tool_calls_capped.ruby_llm event. It's off by default. By @​crmne. (#1668)

Fixed

  • A tool that already acted doesn't run again when another one raises. When a tool raised during complete on a persisted chat, the finished results of its round were deleted, so the model called a tool that had already sent the email or created the record a second time. Finished calls now keep their results and the rest are closed as unfinished, as when a chat is cancelled. By @​crmne; thanks @​LuisFelipeRisch. (#1660, #1664)
  • No more deadlocks on Postgres when a reply saves. With acts_as_message touch_chat: true, saving an answer wrote the chat row twice in one transaction, so Postgres locked every row the chat points to, such as its account or schedule. App code that locked one of those rows and waited on another could deadlock with a reply. The answer now saves with one write to the chat, and the chat is touched right after, in a transaction of its own, so its after_touch and after_commit callbacks still run. By @​crmne. (#1655)
  • Keep a message sent while another job starts a reply. A message sent with ask_later just as another process claimed the chat could be saved with no reply. It is now queued and answered when that run ends. By @​yorzi. (#1646, #1647)
  • Record what a failed judgment cost. A judgment whose answer couldn't be parsed was recorded with no tokens and no cost, although the provider billed it. The usage it reported is now saved first, on System One, OpenRouter and OpenAI judgments alike, and the parse error still reaches your code. By @​crmne; thanks @​josh-sanders. (#1614, #1658)
  • Approve a tool call without loading the whole chat. approve on a persisted chat used to build the chat and its transcript just to record the decision. It now records it straight on the tool call. By @​costajohnt; thanks @​stephanmoneybird. (#1644, #1645)
  • Read the current version of a file. A folder file store could show the text it had converted from an earlier version of a file with the same size and modification time, and mark the new version as read. Converted text is now tied to the exact bytes it came from. By @​yorzi. (#1648, #1656)
  • Convert a file by the type it was stored with. A file stored with an explicit type and no telling extension, such as captions saved as application/x-subrip, now goes to that type's converter. By @​yorzi. (#1649, #1652)
  • Keep every type of a union in Gemini batches. A schema field such as ["string", "integer", "null"] lost every type after the first, or reached Gemini in a form it rejects, when the chat went through RubyLLM.batch. Batches now send it the way Google's own SDK does. By @​crmne; thanks @​yorzi for the report and the approach. (#1665, #1667)
  • Submit list answers from the generated question cards. A question with a free-form list field, such as tags, lost its answer when submitted from the chat UI. Regenerate the chat UI to pick up the fix. By @​yorzi. (#1650, #1653)

Thanks

Thanks to @​yorzi, @​costajohnt, @​LuisFelipeRisch, @​stephanmoneybird, and @​josh-sanders for the fixes and reports in this release.

... (truncated)

Changelog

Sourced from ruby_llm's changelog.

RubyLLM 2.2.2 loads the Ruby classes apps keep in app/skills again, keeps model rows your chats still use when a registry refresh runs without a foreign key, and shows each choice's title on the generated question cards.

bundle add ruby_llm --version 2.2.2

Already on 2.2? Run bundle update ruby_llm. No schema or code changes are needed.

Fixed

  • Your own classes in app/skills load again. 2.2 told the Rails autoloader to skip the whole app/skills folder, so an app that keeps its own Ruby classes there got NameError for every one of them after upgrading, whether or not it used RubyLLM skills. Now only skill folders are skipped: any folder holding a SKILL.md, at any depth, including skill folders that are symbolic links. Everything else in app/skills loads as it did in 2.1, and a skill you add while the development server runs is skipped on the next reload, with no restart. By @​crmne; thanks @​sebscholl. (#1671, #1675)
  • A model refresh keeps the models your chats use, with or without a foreign key. Refreshing the model registry deleted ruby_llm_models rows it no longer listed, and only the foreign key from chats stopped it from deleting rows a chat still pointed at. Schemas without that key, such as MySQL setups that skip foreign keys, lost those rows and left chats pointing at nothing. Referenced rows are now kept and marked unlisted, as they are with the foreign key. By @​yshmarov. (#1670)

New

  • Question cards show each choice's title. When a tool's ask or an MCP server gives its choices titles, the generated chat UI showed the raw values, such as 17 and 42, instead of "River bank" and "Money bank". The cards now label each button and option with its title and still submit the value. Your own UI can read the titles with field.choice_titles, which understands oneOf and items.anyOf with const and title, and enumNames. Regenerate the chat UI to pick it up. By @​kryzhovnik. (#1661)

Thanks

Thanks to @​yshmarov and @​kryzhovnik for the fixes in this release, and to @​sebscholl for reporting the app/skills regression.

Full changelog: crmne/ruby_llm@v2.2.1...v2.2.2

Commits

Updates ruby_llm-schema from 0.4.0 to 1.0.0

Release notes

Sourced from ruby_llm-schema's releases.

v1.0.0

RubyLLM::Schema is now Schematist. Schematist is a general purpose JSON Schema DSL that emits Draft 2020-12 schemas. Trapping that inside another gem's namespace was a disservice to anyone looking for a great JSON Schema DSL.

gem 'schematist'                         # was: gem 'ruby_llm-schema'
class Person < Schematist::Schema        # was: RubyLLM::Schema
end

Breaking

  • to_json_schema returns a Draft 2020-12 document with string keys. The old {name:, description:, schema:} wrapper was OpenAI's response_format shape, and building that belongs in whatever talks to the provider.
  • strict is gone. It's an OpenAI request flag, not a JSON Schema keyword.
  • Errors moved up a level: Schematist::ValidationError, not RubyLLM::Schema::ValidationError.
  • RubyLLM::Helpers is now Schematist::Helpers.

A final ruby_llm-schema 1.0.0 depends on this gem and aliases the old constants, so RubyLLM::Schema keeps resolving while you migrate.

New

Schematist now speaks most of Draft 2020-12:

  • Composition: all_of, one_of, none_of join any_of
  • Unevaluated: unevaluated_properties: and unevaluated_items:
  • Object keys: min_properties:, max_properties:, keys for propertyNames, keys_matching for patternProperties
  • Arrays: unique: for uniqueItems, tuple for prefixItems, contains with min: / max:
  • Annotations: title, description, default, examples, deprecated, read_only, write_only, as keywords or inside the block
  • Encoded content: content_encoding:, content_media_type:, content_schema
  • Core keywords: $id, $anchor, $comment, $dynamicAnchor, $dynamicRef, $vocabulary
  • Boolean and raw schemas: any_schema, no_schema, and raw for anything the DSL doesn't model
  • const on every primitive, and greater_than: / less_than: for the exclusive bounds

Runtime values. Any value can be a proc, resolved when the document is rendered, so one schema class gives you a different document per instance:

string :role, enum: -> { @account.roles.pluck(:name) }

No runtime dependencies.

Fixed

number, integer, boolean and null didn't accept a block, so integer(:a) { title "A" } dropped the annotation silently instead of raising.

Changelog

Sourced from ruby_llm-schema's changelog.

Release process

  1. Bump the version in lib/schematist/version.rb
  2. Run bundle install
  3. Write the release notes in packaging/release-notes/vX.Y.Z.md
  4. Commit the changes with a message like "Bump version to X.Y.Z"
  5. Run bundle exec rake release:prepare
  6. Push to main
  7. GitHub Actions will publish the gem if the version is not already on RubyGems
  8. GitHub Actions will create the vX.Y.Z tag and a GitHub Release whose description is packaging/release-notes/vX.Y.Z.md, if they do not already exist

Note that step 7 fires on any change to lib/schematist/version.rb, so a version bump on main is a release. Hold the bump until everything else for that release has landed.

If the notes file is missing, the release gate fails before anything is published. Pushing the notes file reruns it and completes the release.

The ruby_llm-schema compatibility gem

compat/ruby_llm-schema is the final release of the old name. It depends on schematist ~> 1.0 and aliases RubyLLM::Schema, so anyone still on it picks up every schematist 1.x release from a normal bundle update. It does not need a release of its own when schematist ships a new minor, and it should not get one: releasing a deprecated gem on a schedule makes it look maintained.

It publishes from CI like schematist does, in a job that runs after schematist so the dependency resolves. The version lives in compat/ruby_llm-schema/ruby_llm-schema.gemspec, and the job is a no-op once that version is on RubyGems. To release it by hand instead:

cd compat/ruby_llm-schema
gem build ruby_llm-schema.gemspec
gem push ruby_llm-schema-1.0.0.gem

Revisit at schematist 2.0. ~> 1.0 will freeze those users on 1.x, so that is the point to either cut a compatibility 2.0 or let the old name go.

Commits
  • ac1a66e Point contributor docs at the new repo name
  • 388b179 Drop the zeitwerk dependency, keep the layout
  • 40f3b65 Follow Zeitwerk conventions for file layout
  • fa30b95 Rename the gem to Schematist
  • f4b436c Accept blocks on every primitive property
  • d2269a9 Remove the provider envelope from schema output
  • dfac29c Return a Draft 2020-12 document from to_json_schema (#57)
  • 761de5c Support runtime schema values (#47)
  • 84d043b Add boolean and raw schemas (#55)
  • 1a3f042 Add core identifier and reference keywords (#54)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the production-dependencies group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [puma](https://github.com/puma/puma) | `8.0.2` | `8.1.0` |
| [solid_queue](https://github.com/rails/solid_queue) | `1.7.0` | `1.7.2` |
| [bootsnap](https://github.com/rails/bootsnap) | `1.26.0` | `1.26.1` |
| [thruster](https://github.com/basecamp/thruster) | `0.1.26` | `0.1.27` |
| [ruby_llm](https://github.com/crmne/ruby_llm) | `2.1.0` | `2.2.2` |
| [ruby_llm-schema](https://github.com/crmne/schematist) | `0.4.0` | `1.0.0` |



Updates `puma` from 8.0.2 to 8.1.0
- [Release notes](https://github.com/puma/puma/releases)
- [Changelog](https://github.com/puma/puma/blob/main/History.md)
- [Commits](puma/puma@v8.0.2...v8.1.0)

Updates `solid_queue` from 1.7.0 to 1.7.2
- [Release notes](https://github.com/rails/solid_queue/releases)
- [Commits](rails/solid_queue@v1.7.0...v1.7.2)

Updates `bootsnap` from 1.26.0 to 1.26.1
- [Release notes](https://github.com/rails/bootsnap/releases)
- [Changelog](https://github.com/rails/bootsnap/blob/main/CHANGELOG.md)
- [Commits](rails/bootsnap@v1.26.0...v1.26.1)

Updates `thruster` from 0.1.26 to 0.1.27
- [Changelog](https://github.com/basecamp/thruster/blob/main/CHANGELOG.md)
- [Commits](basecamp/thruster@v0.1.26...v0.1.27)

Updates `ruby_llm` from 2.1.0 to 2.2.2
- [Release notes](https://github.com/crmne/ruby_llm/releases)
- [Changelog](https://github.com/crmne/ruby_llm/blob/main/release-notes.md)
- [Commits](crmne/ruby_llm@v2.1.0...v2.2.2)

Updates `ruby_llm-schema` from 0.4.0 to 1.0.0
- [Release notes](https://github.com/crmne/schematist/releases)
- [Changelog](https://github.com/crmne/schematist/blob/main/RELEASE.md)
- [Commits](crmne/schematist@v0.4.0...v1.0.0)

---
updated-dependencies:
- dependency-name: puma
  dependency-version: 8.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: solid_queue
  dependency-version: 1.7.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: bootsnap
  dependency-version: 1.26.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: thruster
  dependency-version: 0.1.27
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: ruby_llm
  dependency-version: 2.2.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: ruby_llm-schema
  dependency-version: 1.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code labels Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants