This repository was archived by the owner on Jun 11, 2026. It is now read-only.
chore(deps): raise gemspec constraints for security patches — 2026-06-10 - #2
Open
jondkinney wants to merge 1 commit into
Open
chore(deps): raise gemspec constraints for security patches — 2026-06-10#2jondkinney wants to merge 1 commit into
jondkinney wants to merge 1 commit into
Conversation
Widen the carrierwave constraint from `~> 1.1` (which capped resolution at 1.3.4) to `>= 2.2.7, < 3` so the security-patched 2.2.7 release is admissible. The gem's `cache!` override loads and works unchanged under carrierwave 2.x. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jondkinney
marked this pull request as ready for review
June 10, 2026 18:54
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Raise gemspec constraints for security patches
This gem's version constraints capped one or more dependencies below their security-patched versions, holding every consuming app on vulnerable releases. This PR raises the blocking constraints so the patched versions are admissible, with code/test changes for any breaking upgrade.
Constraints that were blocking a patch