chore(deps): bump json from 2.19.1 to 2.19.2

[dependabot]

Bumps json from 2.19.1 to 2.19.2.

Release notes

Sourced from json's releases.

v2.19.2

What's Changed

• Fix a format string injection vulnerability in JSON.parse(doc, allow_duplicate_key: false). CVE-2026-33210

Full Changelog: ruby/json@v2.19.1...v2.19.2

Changelog

Sourced from json's changelog.

2026-03-18 (2.19.2)

• Fix a format string injection vulnerability in JSON.parse(doc, allow_duplicate_key: false). CVE-2026-33210.

Commits

• 54f8a87 Release 2.19.2
• 393b41c Fix a format string injection vulnerability
• dbf6bb1 Merge pull request #953 from ruby/dependabot/github_actions/actions/create-gi...
• 7187315 Bump actions/create-github-app-token from 2 to 3
• See full diff 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-03-21 14:11 UTC · Rule: dependabot
• ✅ Checks started · on draft merge queue: embarking main (b4e62ad) and #898 together #899
• 🚫 Left the queue — 2026-03-21 14:11 UTC · at 697a2efbb327e3c5dbcd604f17135cc829df43e8

This pull request spent 8 seconds in the queue, including 1 second running CI.

Required conditions to merge

• base=master
• status-success=docker-test
• status-success=hadolint
• status-success=ruby
• any of [🛡 GitHub branch protection]:
  • check-neutral = frontend
  • check-skipped = frontend
  • check-success = frontend
• any of [🛡 GitHub branch protection]:
  • check-neutral = ruby
  • check-skipped = ruby
  • check-success = ruby
• author=dependabot[bot]
  • chore(deps): bump json from 2.19.1 to 2.19.2 #898

Reason

Pull request #898 has been dequeued

merge conditions unmatch:

• base=master
• status-success=docker-test
• status-success=hadolint
• status-success=ruby
• any of [🛡 GitHub branch protection]:
  • check-neutral = frontend
  • check-skipped = frontend
  • check-success = frontend
• any of [🛡 GitHub branch protection]:
  • check-neutral = ruby
  • check-skipped = ruby
  • check-success = ruby
• author=dependabot[bot]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-03-21 15:15 UTC · Rule: dependabot
• ✅ Checks started · on draft merge queue: embarking main (ee7df73) and #898 together #905
• 🚫 Left the queue — 2026-03-22 13:00 UTC · at f18cfa23d1b020c4847659a2eb1371e5472a06c7

This pull request spent 21 hours 44 minutes 16 seconds in the queue, including 35 seconds running CI.

Required conditions to merge

• check-success=docker-test (false)
• check-success=docker-test (true)
• status-success=ruby
• any of [🛡 GitHub branch protection]:
  • check-neutral = frontend
  • check-skipped = frontend
  • check-success = frontend
• any of [🛡 GitHub branch protection]:
  • check-neutral = ruby
  • check-skipped = ruby
  • check-success = ruby
• author=dependabot[bot]
  • chore(deps): bump json from 2.19.1 to 2.19.2 #898
• base=main
• status-success=hadolint

Reason

New commits have been added to the draft pull request that were not made by Mergify

Hint

If you want to requeue this pull request, you can post a @mergifyio queue comment.

[gildesmarais]

@dependabot recreate

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[dependabot]

Looks like this PR is closed. If the branch still exists, you can re-open the PR and then use @dependabot rebase or @dependabot recreate. If the branch was deleted, Dependabot will create a new PR on the next scheduled run, or you can trigger an update from the Dependency graph page.