Bump activesupport from 7.2.3 to 7.2.3.1 in /example/ios#121
Bump activesupport from 7.2.3 to 7.2.3.1 in /example/ios#121dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [activesupport](https://github.com/rails/rails) from 7.2.3 to 7.2.3.1. - [Release notes](https://github.com/rails/rails/releases) - [Changelog](https://github.com/rails/rails/blob/v8.1.2.1/activesupport/CHANGELOG.md) - [Commits](rails/rails@v7.2.3...v7.2.3.1) --- updated-dependencies: - dependency-name: activesupport dependency-version: 7.2.3.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| highline (~> 2.0.0) | ||
| concurrent-ruby (1.3.6) | ||
| connection_pool (2.5.5) | ||
| connection_pool (3.0.2) |
There was a problem hiding this comment.
Unintended major version bump of connection_pool to 3.0
Medium Severity
The connection_pool gem was silently bumped from 2.5.5 to 3.0.2 as a side effect of regenerating the lockfile. connection_pool 3.0 introduced a breaking change—switching initialize from positional to keyword arguments—that is known to be incompatible with ActiveSupport 7.2.x cache stores (causing ArgumentError: wrong number of arguments). It also requires Ruby >= 3.2.0. The activesupport constraint connection_pool (>= 2.2.5) lacks an upper bound, so Bundler resolved to 3.x. Pinning connection_pool to < 3 in the Gemfile would prevent this.
Bumps activesupport from 7.2.3 to 7.2.3.1.
Release notes
Sourced from activesupport's releases.
... (truncated)
Commits
ba76fcaPreparing for 7.2.3.1 release8a379f4Update changelogb54a4b3Improve performance of NumberToDelimitedConverterc1ad0e8FixSafeBuffer#%to preserve unsafe statusebd6be1NumberConverter: reject scientific notation4a155f1Lock some dependenciesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.
Note
Low Risk
Low risk lockfile-only change; primary impact is dependency resolution for iOS tooling, though bundler/cocoapods behavior could change slightly due to transitive version bumps.
Overview
Updates
example/ios/Gemfile.lockto bumpactivesupportfrom7.2.3to7.2.3.1.This also adjusts resolved constraints/versions for transitive gems, notably tightening
minitestto< 6underactivesupportand bumpingconnection_poolto3.0.2.Written by Cursor Bugbot for commit 14fe6e0. This will update automatically on new commits. Configure here.