Skip to content

Comments

Fixup code for use with rackup gem (may be used with rack 3) (#3061)#10

Open
MitchLewis930 wants to merge 1 commit intopr_060_beforefrom
pr_060_after
Open

Fixup code for use with rackup gem (may be used with rack 3) (#3061)#10
MitchLewis930 wants to merge 1 commit intopr_060_beforefrom
pr_060_after

Conversation

@MitchLewis930
Copy link

@MitchLewis930 MitchLewis930 commented Jan 30, 2026

PR_060


Note

Medium Risk
Touches server boot/handler registration and default selection logic across Rack 2 vs Rack 3, so mis-detection or constant-loading differences could break app startup in some environments.

Overview
Updates Puma’s Rack handler integration to support Rack 3’s extraction of rackup.

When Rackup is present, Puma now defines/registers its handler under Rackup::Handler and uses it for the default handler selection; for Rack < 3 it continues to use Rack::Handler, and it raises a clear error if Rack 3 is used without rackup. Tests are updated to run against either rack or rackup based on PUMA_CI_RACK_2, and the Gemfile conditionally adds the rackup dependency for non-Rack-2 CI runs.

Written by Cursor Bugbot for commit 8092bf8. This will update automatically on new commits. Configure here.

* Fixup code for use with rackup gem (may be used with rack 3)

* Update rack_default.rb

* Update puma.rb, use `include` instead of `module_eval`

* Changes per comments
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.

2 participants