Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit e2285da

Browse files
authoredApr 29, 2025··
Bump connection_pool from 2.5.2 to 2.5.3
Bumps [connection_pool](https://github.com/mperham/connection_pool) from 2.5.2 to 2.5.3. - [Changelog](https://github.com/mperham/connection_pool/blob/main/Changes.md) - [Commits](mperham/connection_pool@v2.5.2...v2.5.3) --- updated-dependencies: - dependency-name: connection_pool dependency-version: 2.5.3 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
1 parent 3d38628 commit e2285da

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed
 

‎Gemfile.lock

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ GEM
9696
commonmarker (2.3.0-x86_64-darwin)
9797
commonmarker (2.3.0-x86_64-linux)
9898
concurrent-ruby (1.3.5)
99-
connection_pool (2.5.2)
99+
connection_pool (2.5.3)
100100
counter_culture (3.10.0)
101101
activerecord (>= 4.2)
102102
activesupport (>= 4.2)
@@ -447,7 +447,7 @@ CHECKSUMS
447447
commonmarker (2.3.0-x86_64-darwin) sha256=65919fe63bc1e01319d958351ae611cc913bd2a8aa3f1a4f3fb3d12e82fbc568
448448
commonmarker (2.3.0-x86_64-linux) sha256=a6f2b523be0c3e4752aaf55cc5026239080b81f91bd2f72226b6e71919d204d0
449449
concurrent-ruby (1.3.5) sha256=813b3e37aca6df2a21a3b9f1d497f8cbab24a2b94cab325bffe65ee0f6cbebc6
450-
connection_pool (2.5.2) sha256=c121d090f8217911f960c7b628bf2bf1b1444f284fd854edc188821c4f602108
450+
connection_pool (2.5.3) sha256=cfd74a82b9b094d1ce30c4f1a346da23ee19dc8a062a16a85f58eab1ced4305b
451451
counter_culture (3.10.0) sha256=7585034e6d67d5d23c9abb4267ebe2d472121a6760f2eda7daa894078539a802
452452
crack (1.0.0) sha256=c83aefdb428cdc7b66c7f287e488c796f055c0839e6e545fec2c7047743c4a49
453453
crass (1.0.6) sha256=dc516022a56e7b3b156099abc81b6d2b08ea1ed12676ac7a5657617f012bd45d

0 commit comments

Comments
 (0)
Please sign in to comment.