Skip to content

Bump puma from 6.6.0 to 8.0.0 #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

Bump puma from 6.6.0 to 8.0.0 #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Gemfile.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -319,7 +319,7 @@ GEM
date
stringio
public_suffix (6.0.2)
puma (6.6.0)
puma (8.0.0)

@chatgpt-codex-connector chatgpt-codex-connector Bot Apr 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Set an explicit bind host before adopting Puma 8

This upgrade changes Puma’s production default bind from 0.0.0.0 to ::, but our Puma config only calls port ENV.fetch("PORT", 3000) and does not set a host explicitly. In environments where IPv6 is present but IPv4-mapped IPv6 is disabled (net.ipv6.bindv6only=1), the app will no longer accept IPv4 traffic on $PORT, causing production health checks or ingress connections to fail after this dependency bump.

Useful? React with 👍 / 👎.

nio4r (~> 2.0)
raabro (1.4.0)
racc (1.8.1)
Expand Down