Skip to content

chore(deps): bump solid_queue_monitor from 2.2.0 to 2.2.1#723

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/solid_queue_monitor-2.2.1
Open

chore(deps): bump solid_queue_monitor from 2.2.0 to 2.2.1#723
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/solid_queue_monitor-2.2.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 14, 2026

Copy link
Copy Markdown
Contributor

Bumps solid_queue_monitor from 2.2.0 to 2.2.1.

Release notes

Sourced from solid_queue_monitor's releases.

v2.2.1

Highlights

Patch release fixing an activity-chart crash on multi-database deployments.

Fixed

  • Activity chart no longer crashes the dashboard on multi-database setups where Solid Queue runs on a different engine than the host app's primary database (e.g. a MySQL primary with a dedicated PostgreSQL queue database via config.solid_queue.connects_to). The SQL dialect for the time-bucketing query is now detected from the Solid Queue model's own connection instead of ActiveRecord::Base, so a PG::UndefinedFunction: function unix_timestamp(...) does not exist error is no longer raised. Single-database and same-engine setups are unaffected. (#42)

Full Changelog: vishaltps/solid_queue_monitor@v2.2.0...v2.2.1

Changelog

Sourced from solid_queue_monitor's changelog.

[2.2.1] - 2026-07-13

Fixed

  • Activity chart no longer crashes the dashboard on multi-database setups where Solid Queue runs on a different engine than the host app's primary database (e.g. a MySQL primary with a dedicated PostgreSQL queue database via config.solid_queue.connects_to). The SQL dialect for the time-bucketing query is now detected from the Solid Queue model's own connection instead of ActiveRecord::Base, so a PG::UndefinedFunction: function unix_timestamp(...) does not exist error is no longer raised. Single-database and same-engine setups are unaffected. (#42)
Commits

Dependabot compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [solid_queue_monitor](https://github.com/vishaltps/solid_queue_monitor) from 2.2.0 to 2.2.1.
- [Release notes](https://github.com/vishaltps/solid_queue_monitor/releases)
- [Changelog](https://github.com/vishaltps/solid_queue_monitor/blob/main/CHANGELOG.md)
- [Commits](vishaltps/solid_queue_monitor@v2.2.0...v2.2.1)

---
updated-dependencies:
- dependency-name: solid_queue_monitor
  dependency-version: 2.2.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

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 Jul 14, 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