FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

build(deps): bump the bundler group across 2 directories with 1 update by dependabot[bot] · Pull Request #464 · intercom/intercom-react-native · GitHub

/ intercom-react-native Public

build(deps): bump the bundler group across 2 directories with 1 update - #464

Open
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/bundler/examples/with-notifications/bundler-3c688094d7
ConversationCommits (3)ChecksFiles changed
Open

build(deps): bump the bundler group across 2 directories with 1 update#464
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/bundler/examples/with-notifications/bundler-3c688094d7

Conversation

dependabot Bot commented on behalf of github Aug 9, 2026

Copy link
Copy Markdown
Contributor

Bumps the bundler group with 1 update in the /examples/with-notifications directory: json.
Bumps the bundler group with 1 update in the / directory: json.

Updates json from 2.20.0 to 2.21.2

Release notes

Sourced from json's releases.

v2.21.2

What's Changed

Full Changelog: ruby/json@v2.21.1...v2.21.2

v2.21.0

What's Changed

  • JSON.generate now accept a sort_keys option, which takes either a boolean or a block.
  • Added #empty? and #partial_value? methods on JSON::ResumableParser.
  • Numerous correctness and performance fixes for JSON::ResumableParser.
  • Avoid triggering Ruby's float out of range warning when parsing out of range numbers.
  • Declare C types with Ruby 4.1 RUBY_TYPED_THREAD_SAFE_FREE.

Full Changelog: ruby/json@v2.20.0...v2.21.0

Changelog

Sourced from json's changelog.

2026-07-31 (2.21.2)

2026-07-13 (2.21.1)

  • Fix a compilation issue on Window and Microsoft Visual C++.

2026-07-12 (2.21.0)

  • JSON.generate now accept a sort_keys option, which takes either a boolean or a block.
  • Added #empty? and #partial_value? methods on JSON::ResumableParser.
  • Numerous correctness and performance fixes for JSON::ResumableParser.
  • Avoid triggering Ruby's float out of range warning when parsing out of range numbers.
  • Declare C types with Ruby 4.1 RUBY_TYPED_THREAD_SAFE_FREE.
Commits
  • 5a32e43 Release 2.21.2
  • 2c332bf Also don't compute ResumableParser cursor position for warning
  • 5499aa5 Improve max_nesting documentation
  • 499d9bc Fix the parser benchmark bytes report
  • f5fc245 Pass '-mno-outline' to the compiler (if supported) to prevent function outlin...
  • fd61def Release 2.21.1
  • db70b14 Rely on Ruby's HAVE_BUILTIN___BUILTIN_CLZLL
  • 9be0e8e Release 2.21.0
  • d1299d4 Avoid re-decoding an incomplete number on every ResumableParser chunk
  • cc010c4 Fix ResumableParser losing tokens before a feed-boundary suspension
  • Additional commits viewable in compare view

Updates json from 2.10.2 to 2.19.9

Release notes

Sourced from json's releases.

v2.21.2

What's Changed

Full Changelog: ruby/json@v2.21.1...v2.21.2

v2.21.0

What's Changed

  • JSON.generate now accept a sort_keys option, which takes either a boolean or a block.
  • Added #empty? and #partial_value? methods on JSON::ResumableParser.
  • Numerous correctness and performance fixes for JSON::ResumableParser.
  • Avoid triggering Ruby's float out of range warning when parsing out of range numbers.
  • Declare C types with Ruby 4.1 RUBY_TYPED_THREAD_SAFE_FREE.

Full Changelog: ruby/json@v2.20.0...v2.21.0

Changelog

Sourced from json's changelog.

2026-07-31 (2.21.2)

2026-07-13 (2.21.1)

  • Fix a compilation issue on Window and Microsoft Visual C++.

2026-07-12 (2.21.0)

  • JSON.generate now accept a sort_keys option, which takes either a boolean or a block.
  • Added #empty? and #partial_value? methods on JSON::ResumableParser.
  • Numerous correctness and performance fixes for JSON::ResumableParser.
  • Avoid triggering Ruby's float out of range warning when parsing out of range numbers.
  • Declare C types with Ruby 4.1 RUBY_TYPED_THREAD_SAFE_FREE.
Commits
  • 5a32e43 Release 2.21.2
  • 2c332bf Also don't compute ResumableParser cursor position for warning
  • 5499aa5 Improve max_nesting documentation
  • 499d9bc Fix the parser benchmark bytes report
  • f5fc245 Pass '-mno-outline' to the compiler (if supported) to prevent function outlin...
  • fd61def Release 2.21.1
  • db70b14 Rely on Ruby's HAVE_BUILTIN___BUILTIN_CLZLL
  • 9be0e8e Release 2.21.0
  • d1299d4 Avoid re-decoding an incomplete number on every ResumableParser chunk
  • cc010c4 Fix ResumableParser losing tokens before a feed-boundary suspension
  • 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
    You can disable automated security fix PRs for this repo from the Security Alerts page.

build(deps): bump the bundler group across 2 directories with 1 update
73bb743 
Bumps the bundler group with 1 update in the /examples/with-notifications directory: [json](https://github.com/ruby/json).
Bumps the bundler group with 1 update in the / directory: [json](https://github.com/ruby/json).


Updates `json` from 2.20.0 to 2.21.2
- [Release notes](https://github.com/ruby/json/releases)
- [Changelog](https://github.com/ruby/json/blob/master/CHANGES.md)
- [Commits](ruby/json@v2.20.0...v2.21.2)

Updates `json` from 2.10.2 to 2.19.9
- [Release notes](https://github.com/ruby/json/releases)
- [Changelog](https://github.com/ruby/json/blob/master/CHANGES.md)
- [Commits](ruby/json@v2.20.0...v2.21.2)

---
updated-dependencies:
- dependency-name: json
  dependency-version: 2.21.2
  dependency-type: indirect
  dependency-group: bundler
- dependency-name: json
  dependency-version: 2.19.9
  dependency-type: indirect
  dependency-group: bundler
...

Signed-off-by: dependabot[bot] <support@github.com>
dependabot Bot added dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code labels Aug 9, 2026

ems-pr-review Bot commented Aug 9, 2026

Copy link
Copy Markdown

It looks like you are reviewing a Dependabot upgrade PR! 🛠️
That’s great! Keeping our packages up to date to fix security issues in our stack is super important. Team Application Security wants to help make this process as easy and low friction as possible while still moving at pace.

We aim to merge Dependabot PRs within the below timeframes. The objectives are based on the severity of the security vulnerability we are mitigating with the upgrade:

Severity Target Merge (days)
CRITICAL 7 days
HIGH 14 days
MEDIUM 30 days
LOW 90 days

🎯 Target merge date for this PR: 07/11/2026 🎯

FAQ

What if we aren’t vulnerable to this particular CVE? Do we still have to upgrade the package? It’s still a good idea to upgrade the package if we can. With new code patterns and paths being introduced every day, we have no guarantee that we won’t later make ourselves vulnerable. Keeping packages up to date as a matter of due course is also good hygiene. What if we’re not vulnerable and upgrading is going to be a lot of work? In these cases it’s a good idea to list out the steps you took to confirm we are not vulnerable in this PR. The PR can then be closed and the corresponding Dependabot Alert should be dismissed with the triage steps included as a comment. Please get in touch with Team Application Security via #ask-security before dismissing any CRITICAL alerts. This is a major version upgrade that requires substantial code refactoring. What should I do? If the upgrade requires substantial refactoring then it is possible that we will miss the objectives we have outlined above. In these cases, you should add the dependabot-refactor-required label to this PR and ping #ask-security for further advice.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

ems-security-compliance[bot] ems-security-compliance[bot] approved these changes

Assignees

No one assigned

Labels

alert-severity-LOW dependabot-semver-unknown dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants

Back | FazBrowse Home | New Git URL