Skip to content

Bump the production-dependencies group with 4 updates - #266

Merged
Un3x merged 1 commit into
mainfrom
dependabot/bundler/production-dependencies-5ca47eeb28
Nov 16, 2026
Merged

Un3x merged 1 commit into
mainfrom
dependabot/bundler/production-dependencies-5ca47eeb28

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 4 updates: view_component, ransack, kaminari and solid_queue.

Updates view_component from 4.20.0 to 4.23.0

Release notes

Sourced from view_component's releases.

4.23.0

  • Restore request-dependent URL generation when using render_preview inside with_request_url.

    Joel Hawksley

  • Speed up cold cache digests by skipping the # Template Dependency: scan for sources that declare none, and by not translating class names in synthetic templates, which only declare paths.

    Erik Axel Nielsen

4.22.0

  • Comment on release pull requests with benchmark results compared to the previous release.

    Joel Hawksley

  • Reduce source-file reads and dependency-scanning allocations during cold cache digests and boot-time precomputation.

    Joel Hawksley

  • Share sidecar directory listings and source reads during cold cache digests, and hash shared Ruby and sidecar files once per digest computation or boot-time precomputation.

    Joel Hawksley

  • Avoid missing-template digest errors for unresolvable interpolated render paths in components and included helpers.

    Joel Hawksley

  • Cover shared helper dependencies in the boot benchmark and add a cold cache digest benchmark to the CI performance check.

    Joel Hawksley

  • Speed up cache digests of components that render shared dependencies, such as a helper module included by most components. The Digestor looks a template up once per edge of the tree rather than once per component, so each synthetic template was rebuilt, and its sources re-parsed, for every place it was rendered from, and every component digested at boot rebuilt the tree of everything it renders. Templates, dependencies and parsed sources are now shared within one digest computation and across boot-time precomputation, and dependencies whose digest is already known are no longer walked again. On an app with 1,547 components, one cold digest drops from 70 s to 0.5 s and boot-time precomputation from 144 s to 13 s, with identical digests.

    Erik Axel Nielsen

4.21.0

  • Avoid NameError during eager loading when components include modules with temporary names.

    Joel Hawksley

  • Avoid repeated scanning of unterminated ERB tags during cache dependency discovery.

    Joel Hawksley

  • Skip dependency compilation for static ERB markup and literal templates while preserving helper-rendered component tracking.

    Joel Hawksley

... (truncated)

Changelog

Sourced from view_component's changelog.

4.23.0

  • Restore request-dependent URL generation when using render_preview inside with_request_url.

    Joel Hawksley

  • Speed up cold cache digests by skipping the # Template Dependency: scan for sources that declare none, and by not translating class names in synthetic templates, which only declare paths.

    Erik Axel Nielsen

4.22.0

  • Comment on release pull requests with benchmark results compared to the previous release.

    Joel Hawksley

  • Reduce source-file reads and dependency-scanning allocations during cold cache digests and boot-time precomputation.

    Joel Hawksley

  • Share sidecar directory listings and source reads during cold cache digests, and hash shared Ruby and sidecar files once per digest computation or boot-time precomputation.

    Joel Hawksley

  • Avoid missing-template digest errors for unresolvable interpolated render paths in components and included helpers.

    Joel Hawksley

  • Cover shared helper dependencies in the boot benchmark and add a cold cache digest benchmark to the CI performance check.

    Joel Hawksley

  • Speed up cache digests of components that render shared dependencies, such as a helper module included by most components. The Digestor looks a template up once per edge of the tree rather than once per component, so each synthetic template was rebuilt, and its sources re-parsed, for every place it was rendered from, and every component digested at boot rebuilt the tree of everything it renders. Templates, dependencies and parsed sources are now shared within one digest computation and across boot-time precomputation, and dependencies whose digest is already known are no longer walked again. On an app with 1,547 components, one cold digest drops from 70 s to 0.5 s and boot-time precomputation from 144 s to 13 s, with identical digests.

    Erik Axel Nielsen

4.21.0

  • Avoid NameError during eager loading when components include modules with temporary names.

    Joel Hawksley

  • Avoid repeated scanning of unterminated ERB tags during cache dependency discovery.

    Joel Hawksley

  • Skip dependency compilation for static ERB markup and literal templates while preserving helper-rendered component tracking.

    Joel Hawksley

... (truncated)

Commits
  • 05b5c98 Merge pull request #2778 from ViewComponent/release-4-23-0
  • bd38985 release 4.23.0
  • 38567b1 Merge pull request #2777 from ViewComponent/joelhawksley-content-behavior-reg...
  • e93c3f5 Restore compiler override on the original reloaded class
  • ac4183b Exercise preview parameter precedence through rendered output
  • 0a2fcc7 Preserve request routing context when rendering previews
  • 19ea003 Merge pull request #2775 from erikaxel/cache-digest-skip-scans
  • 66a53c6 Skip cache digest scans that can't find anything
  • b1fd129 Merge pull request #2774 from ViewComponent/release-4-22-0
  • abdd4de Fix release CI comments and pending view reloads
  • Additional commits viewable in compare view

Updates ransack from 6.0.1 to 6.1.0

Release notes

Sourced from ransack's releases.

v6.1.0

Security

  • Includes the sort_link / sort_url fix released as 6.0.1. Request params were passed to url_for, so a crafted query string such as ?script_name=javascript:... made sort links run script in the app's origin or point to another site (reflected XSS and open redirect). Ransack now drops url_for's URL options (script_name, host, protocol, only_path, ...) from the params it carries into the link. GHSA-58rx-96gf-w92x.

Compatibility

  • Ruby 3.3 or later and Rails 8.1 or later are required. Ruby 3.2 reached end of life on 2026-03-31, Rails 7.2 on 2026-08-09 and Rails 8.0 on 2026-11-07; none of them receives security fixes. Nothing else changes, so on a supported Ruby and Rails the upgrade needs no code changes. On Ruby 3.2 or Rails 8.0 or earlier, stay on 6.0. — #1756, #1786

Features

  • add_predicate takes arel_node:, a callable that receives the attribute and the cast value and returns a finished Arel node, so a custom predicate can combine conditions without monkey patching Arel::Predications:

    config.add_predicate 'gteq_or_null',
      arel_node: ->(attr, val) { attr.gteq(val).or(attr.eq(nil)) }

    It can't be combined with arel_predicate, has no _any / _all forms, and must return an Arel::Nodes::Node (anything else raises ArgumentError). The result is normalized like a built-in predicate's, and works with null_sentinel. — #1789 by @​agrberg

Bug fixes

Negative predicates on a collection (articles_title_not_eq, tags_name_not_in, notes_note_not_cont, ...) are built as a correlated subquery. 6.1 fixes how that subquery is built and which joins come with it:

  • Calling result twice, or putting two negative conditions on the same collection, no longer raises NoMethodError (undefined method 'table' for nil). This was a regression in 6.0.0: search.result followed by search.result.order_values, a pair of conditions like articles_title_not_eq plus articles_body_not_cont, or an _or_ attribute all failed. — #1746, fixes #1745

  • The subquery reaches the same records the association does. It used to keep only the foreign-key correlation and drop the rest of the join, so it counted rows the association doesn't reach, and returned wrong records without raising:

    • the type column of a polymorphic has_many ... as:: a note on another model with the same id excluded the record
    • the target's default scope: a comment hidden by default_scope still excluded the record
    • the STI type column and the association's own scope
    • an association with a primary_key: option produced invalid SQL; it's now tested on that column

    — #1751, fixes #1747

  • A join something else in the search reads is kept. A sort on the same collection (s: 'articles_title asc', e.g. from a sort_link), or a condition or sort on an association nested under it (articles_comments_body_eq), referenced a join the negative condition had dropped (no such column). The join now stays alongside the subquery. — #1752, fixes #1749

  • A search can be changed after result and evaluated again. Evaluating a search no longer changes it. A sort or condition added afterwards used to reference a dropped join, or an alias (articles_people) the query didn't have. The joins come from the search as it stands when it is evaluated, so clearing a sort or condition also drops its join instead of leaving one behind to repeat records. — #1753, fixes #1750

  • Every collection on the model gets the subquery. It was only built when the attribute name started with the collection's table name, so an STI subclass (story_articles_title_not_eq), a scoped association (published_articles_title_not_eq) or one named differently from its table fell back to a join with a row-level !=, and returned records that do have a matching row. — #1783, fixes #1773

Joins a search adds now line up with the joins the relation already has:

  • A condition nested under an eager-loaded association no longer produces invalid SQL. Article.eager_load(:author).ransack(author_profile_id_not_null: true) joined the profile before the author it hangs off. This was a regression in 6.0.0. — #1768, fixes #1767
  • A direct association and a nested one to the same table stay apart. Comment.ransack(person_name_eq: ..., article_person_name_eq: ...) returned nothing when the nested condition came first, because both conditions were bound to the same join. — #1781, fixes #1775
  • Joins added to a result keep the search on its own joins. result.joins(:target_person) took the table name the search's join expected, so the search's conditions silently filtered the wrong join, and a string join produced invalid SQL. — #1784, fixes #1776

Malformed search params raise Ransack::InvalidSearchError from ransack as well as ransack!. A hand-edited query string such as ?q[g]=x, ?q[c][0]=x or ?q[s][0]=name used to raise ArgumentError, NoMethodError or TypeError from deep inside the node that tripped over it, and an array where a single value belongs (?q[s][0][dir][]=desc, ?q[c][0][p][]=eq) was silently dropped or read as ascending, so rescue_from Ransack::InvalidSearchError turned it into a 500 rather than a 400. InvalidSearchError is an ArgumentError, so existing rescues still work. Also: a hash sort without a direction (s: [{ name: 'title' }]) no longer raises and sorts ascending, and dir: :desc is read instead of falling back to ascending. — #1763

  • A key with a newline in it no longer crashes a search, or searches something else. Key patterns matched line by line, so %0A in a condition or sort key raised NoMethodError, and notable_of_Person_type%0Azzz_name_eq was searched as notable_of_Person_type_name_eq. Such a key is now an unknown key like any other. — #1764
  • Sort link labels are thread-safe. Translate kept the name it was translating on the module, so two requests rendering association sort_links at once could swap labels or raise I18n::MissingInterpolationArgument. — #1765
  • A Time passed to a scope reaches the scope whole. It was splatted through Time#to_a and raised ArgumentError. Only an Array is spread into arguments now. — #1778, fixes #1769
  • Temporary tables, and tables whose names differ only in case, can be searched. No table named X exists was raised because the schema cache didn't list them; Active Record queries them fine. — #1779, fixes #1770
  • An association path in ransackable_attributes is followed. With person_name allowlisted on Article, person_name_cont was bound as articles.person_name and raised no such column. — #1780, fixes #1774

... (truncated)

Commits
  • 15559bd Version 6.1.0 (#1758)
  • c68b1f6 Comment out the case-insensitive SQLite table spec until Rails fixes it (#1800)
  • b7aa297 Spec that the correlated subquery is built from an Arel table (#1796)
  • 608f902 Build correlated subqueries with the model Arel table (#1795)
  • 645520b Run CI against Rails main, allowed to fail (#1798)
  • 1a4ad32 Keep the term as text for LIKE predicates on non-text columns (#1794)
  • 9bbadf1 Require active_support before its core extensions (#1792)
  • fbc3baf Document how to report a vulnerability and how maintainers handle one (#1790)
  • e60ea59 Use the ActiveRecord Hackery logo as the Ransack logo (#1791)
  • 5ba3e81 Add arel_node: let a predicate build a finished Arel node (#1789)
  • Additional commits viewable in compare view

Updates kaminari from 1.3.2 to 1.3.3

Release notes

Sourced from kaminari's releases.

v1.3.3

1.3.3

Enhancements:

Changelog

Sourced from kaminari's changelog.

1.3.3

Enhancements:

Commits
  • e3d7834 Version 1.3.3
  • 551c8cc Test and document the top level format option for all the helpers
  • 09c1988 Support format as a top level option in the pagination helpers
  • See full diff 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

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

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file ruby Pull requests that update ruby code labels Nov 16, 2026
@Un3x

Un3x commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

@dependabot rebase

Bumps the production-dependencies group with 4 updates: [view_component](https://github.com/viewcomponent/view_component), [ransack](https://github.com/activerecord-hackery/ransack), [kaminari](https://github.com/kaminari/kaminari) and [solid_queue](https://github.com/rails/solid_queue).


Updates `view_component` from 4.20.0 to 4.23.0
- [Release notes](https://github.com/viewcomponent/view_component/releases)
- [Changelog](https://github.com/ViewComponent/view_component/blob/main/docs/CHANGELOG.md)
- [Commits](ViewComponent/view_component@v4.20.0...v4.23.0)

Updates `ransack` from 6.0.1 to 6.1.0
- [Release notes](https://github.com/activerecord-hackery/ransack/releases)
- [Changelog](https://github.com/activerecord-hackery/ransack/blob/main/CHANGELOG.md)
- [Commits](activerecord-hackery/ransack@v6.0.1...v6.1.0)

Updates `kaminari` from 1.3.2 to 1.3.3
- [Release notes](https://github.com/kaminari/kaminari/releases)
- [Changelog](https://github.com/kaminari/kaminari/blob/master/CHANGELOG.md)
- [Commits](kaminari/kaminari@v1.3.2...v1.3.3)

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)

---
updated-dependencies:
- dependency-name: view_component
  dependency-version: 4.23.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: ransack
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: kaminari
  dependency-version: 1.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  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
...

Signed-off-by: dependabot[bot] <support@github.com>
@Un3x
Un3x force-pushed the dependabot/bundler/production-dependencies-5ca47eeb28 branch from 0ad7e7b to 1eb25c3 Compare November 16, 2026 14:48
@Un3x
Un3x merged commit 369e7f3 into main Nov 16, 2026
5 checks passed
@Un3x
Un3x deleted the dependabot/bundler/production-dependencies-5ca47eeb28 branch November 16, 2026 14:51
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.

1 participant