Skip to content

Remove activesupport from Gemfile - #3277

Merged
ksss merged 1 commit into
ruby:masterfrom
ksss:remove-activesupport-from-gemfile
Nov 10, 2026
Merged

ksss merged 1 commit into
ruby:masterfrom
ksss:remove-activesupport-from-gemfile

Conversation

@ksss

@ksss ksss commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator

gem "activesupport", "~> 7.0" was added in ee0d187 ("Keep activesupport 7.x because of Ruby 3.1 support"). At that time steep depended on activesupport, and without the pin it resolved to 8.x, which doesn't support Ruby 3.1.

That reason no longer applies:

  • required_ruby_version is now >= 3.3
  • No gem in Gemfile.lock depends on activesupport anymore
  • RBS itself doesn't require "active_support" (the template code stopped using it in Compile without activesupport #2105)

So this removes the entry rather than bumping it. bundle lock only drops activesupport and the gems that were pulled in solely by it (base64, benchmark, connection_pool, i18n, tzinfo); no other versions change.

🤖 Generated with Claude Code

The `~> 7.0` pin was added in ee0d187 to keep Ruby 3.1 working while
steep pulled in activesupport transitively. RBS now requires Ruby 3.3+,
and nothing in the bundle depends on activesupport anymore, so the entry
only installs unused gems.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@ksss
ksss added this pull request to the merge queue Nov 10, 2026
Merged via the queue into ruby:master with commit b9e024e Nov 10, 2026
24 checks passed
@ksss
ksss deleted the remove-activesupport-from-gemfile branch November 10, 2026 04:54
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