Skip to content

Cap view_component below the next major - #160

Merged
tylercschneider merged 2 commits into
mainfrom
chore/view-component-upper-bound
Jul 31, 2026
Merged

Cap view_component below the next major#160
tylercschneider merged 2 commits into
mainfrom
chore/view-component-upper-bound

Conversation

@tylercschneider

Copy link
Copy Markdown
Collaborator

spec.add_dependency "view_component", ">= 2.0" was open-ended — gem build warns about it, and a future ViewComponent 5 with breaking changes would resolve and break installs.

Now ">= 2.0", "< 5".

Why < 5 and not < 4: the lock already resolves view_component 4.9.0, and the suite passes against it. A < 4 cap would have broken the current dev environment.

test/keystone_ui/packaging_test.rb asserts the requirement rejects 5.0.0, so the bound can't quietly go open-ended again. Verified red before the gemspec change.

Folded into 0.6.0's CHANGELOG rather than [Unreleased] — 0.6.0 hasn't been pushed to RubyGems yet, and this changes what that release will contain.

424 runs, 0 failures. Rubocop clean. bundle install still resolves 4.9.0.

🤖 Generated with Claude Code

tylercschneider and others added 2 commits July 31, 2026 16:22
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@tylercschneider
tylercschneider merged commit 299630d into main Jul 31, 2026
5 checks passed
@tylercschneider
tylercschneider deleted the chore/view-component-upper-bound branch July 31, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant