Skip to content

Bump puma from 6.6.0 to 8.0.1 #111

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.1 #111

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.1)

@chatgpt-codex-connector chatgpt-codex-connector Bot May 5, 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.

P2 Badge Preserve IPv4 bind behavior when upgrading to Puma 8

This bump changes runtime behavior in production because config/puma.rb only calls port ENV.fetch("PORT", 3000) and does not set an explicit host/bind; Puma 8 switched the production default bind toward IPv6 (::), so on hosts where IPv6 sockets are v6-only (for example net.ipv6.bindv6only=1), IPv4 load-balancer or health-check traffic can stop reaching the app after deployment. Since this commit upgrades from 6.6.0 to 8.0.1 without pinning bind address, it can introduce an availability regression in IPv4-oriented environments.

Useful? React with 👍 / 👎.

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