fix: use Rack::Files for Rack 3 compatibility#2
Merged
Conversation
Rack::File was removed in Rack 3 (it had been an alias for Rack::Files since Rack 2.1). Rack::Files works on both Rack 2 and 3, so this keeps the gem compatible across consumers while unblocking Rack 3 upgrades. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
gkrimer
approved these changes
Jun 25, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rack 3 removed
Rack::File(an alias forRack::Filessince Rack 2.1).EmberCli::Deploy::File#to_rackstill called it, which raisesuninitialized constant Rack::Fileat boot under Rack 3.Switches to
Rack::Files, which exists in both Rack 2 and 3 — safe for all consumers regardless of their Rack version.Surfaced while upgrading the main app to Rack 3.