puma 8.0.0 → 8.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9b99ab5935b1e99868b96ec9035d05ed00930f4b001053ec99d52a55b6d3eb18
-  data.tar.gz: 6142fbf02efbf35ad5b723715d0a7e080add67f574aeaf16b87e42cc7c54e181
+  metadata.gz: b4bda2b8a9ed5838776f890077459a3db57a8a581b17516434ba9b9cbd5d0f71
+  data.tar.gz: 621365fbc4837c30dc8c7d32de00ceadbcf80db735ae2388aeb0b521414a1b3c
 SHA512:
-  metadata.gz: 4910a1d1200b6c49bf2c32fb569c66d704fd3cd833fce0d2a62da4856ffd6984818fc0a460d02e8acb599a5ea82a83c94ace92530c0cd53d2955400b8b79497c
-  data.tar.gz: 2f726e8fc621aa245c927b7ad9113e33c3d35c78a832bf39363b54e09962e9866e441d3bed2069281d9f17d6bc21839167588df89572dba239e35d11d8e5525c
+  metadata.gz: 321cc06d7e4f77147aeeb44b29b7de9627b5942ef374b93f64a5aa89c85414c761c79833ba61e6accb0fee53ee68cc91f07121d7a74ab106a1091885e806b123
+  data.tar.gz: eb9e6c89473875970b71d2fec792e68c1355ab0dff2dc6d887cd7221449c5c9e20f7030ec3bc3ed8edb18ff50c906697067325a86d040bdc9bfedb5d74566454

data/History.md

@@ -1,3 +1,15 @@
+## 8.0.1 / 2026-04-27
+
+* Bugfixes
+  * Fix `prune_bundler` stripping user-configured `BUNDLE_*` env vars (e.g. `BUNDLE_WITHOUT`) on re-exec, which caused workers to crash on boot ([#3929])
+
+* Performance
+  * Use blocks for debug logging to avoid creating log messages when debug is disabled ([#3920])
+
+* Docs
+  * Fix incorrect hook names in gRPC docs ([#3923])
+  * Reword v8 upgrade guide IPv6 bullet for clarity ([#3928])
+
 ## 8.0.0 / 2026-03-27
 
 * Features
@@ -2323,6 +2335,10 @@ be added back in a future date when a java Puma::MiniSSL is added.
 * Bugfixes
   * Your bugfix goes here <Most recent on the top, like GitHub> (#Github Number)
 
+[#3929]:https://github.com/puma/puma/pull/3929     "PR by Joshua Young, merged 2026-04-26"
+[#3928]:https://github.com/puma/puma/pull/3928     "PR by Nate Berkopec, merged 2026-04-16"
+[#3923]:https://github.com/puma/puma/pull/3923     "PR by Joshua Young, merged 2026-04-10"
+[#3920]:https://github.com/puma/puma/pull/3920     "PR by Petrik de Heus, merged 2026-04-10"
 [#3912]:https://github.com/puma/puma/pull/3912     "PR by Bengt-Ove Hollaender, merged 2026-03-26"
 [#3900]:https://github.com/puma/puma/pull/3900     "PR by Nate Berkopec, merged 2026-03-26"
 [#3894]:https://github.com/puma/puma/pull/3894     "PR by Joshua Young, merged 2026-03-07"

data/docs/8.0-Upgrade.md

@@ -91,7 +91,7 @@ bind 'tcp://0.0.0.0:9292'
 
 Check the following list to see if you're depending on any of these behaviors:
 
-1. If you rely on Puma's default bind from `bin/puma`, Rack handler startup, `port`, or an implicit config file bind, Puma may now listen on `::` and advertise `tcp://[::]:PORT` whenever a non-loopback IPv6 interface is present. If you need the old IPv4 wildcard behavior, set `bind 'tcp://0.0.0.0:9292'`, `port ENV.fetch('PORT', 9292), '0.0.0.0'`, or `set_default_host '0.0.0.0'` explicitly, and review any firewall rules, health checks, deploy scripts, or host-string parsing code that assumed `0.0.0.0` or unbracketed `HOST:PORT` formatting.
+1. Puma will now listen on `::` (IPv6) by default. Previously, it listened to `0.0.0.0` (IPv4). Systems that support both IPv6 and IPv4 (Ubuntu and Mac commonly do) will still support receiving to `0.0.0.0`. See [[the support table in the PR](https://github.com/puma/puma/pull/3847)](https://github.com/puma/puma/pull/3847) for a binding compatibility. For systems that ONLY bind to IPv6 (without IPv4 support) this may be a breaking change. You can overwrite this default behavior by setting `bind 'tcp://0.0.0.0:9292'`, `port ENV.fetch('PORT', 9292), '0.0.0.0'`, or `set_default_host '0.0.0.0'` explicitly to remain IPv4 only. Review any firewall rules, health checks, deploy scripts, or host-string parsing code that assumed `0.0.0.0`, `127.0.0.1`, or unbracketed `HOST:PORT` formatting.
 2. If you explicitly configure `bind 'tcp://[::]:...'`, `bind 'ssl://[::]:...'`, or equivalent `ssl_bind '::', ...`, Puma will now rewrite that unspecified IPv6 bind to `0.0.0.0` when the host has no non-loopback IPv6 interface, and it will warn on boot. If you were using `::` to force IPv6-only behavior or to detect IPv6 availability, switch to a concrete IPv6 address instead of `::`, or ensure the machine actually has a usable IPv6 interface before Puma starts.
 3. `before_thread_start` hooks now receive a `Puma::ServerPluginControl` argument. Update any zero-arity lambdas, method objects, or other strict-arity hook code to accept one argument, for example `before_thread_start { |_control| ... }`, or Puma can raise `ArgumentError` when the hook runs.
 4. On platforms without `SIGINFO`, Puma now traps `SIGPWR`, and `pumactl info` sends `SIGPWR` there. If your supervisor, init script, or container tooling already uses `SIGPWR` for something else, change that wiring before upgrading and update any runbooks that assumed Puma would ignore `SIGPWR`.

data/docs/grpc.md

@@ -15,7 +15,7 @@ To work correctly, gRPC needs these methods called at specific points in the pro
 - `GRPC.postfork_child`: Called in the child process after forking.
 - `GRPC.postfork_parent`: Called in the parent process after forking.
 
-Puma provides hooks such as `on_worker_fork`, `after_worker_fork`, and `on_worker_boot` to execute code during these lifecycle events. Understanding the behavior of these hooks is key to ensuring gRPC operates correctly in a clustered setup.
+Puma provides hooks such as `before_worker_fork`, `after_worker_fork`, and `before_worker_boot` to execute code during these lifecycle events. Understanding the behavior of these hooks is key to ensuring gRPC operates correctly in a clustered setup.
 
 ## The Solution
 
@@ -45,7 +45,7 @@ end
 
 Puma's hooks determine when to call gRPC's lifecycle methods. Each hook plays a specific role in managing the lifecycle during forking:
 
-- **`on_worker_fork`**:
+- **`before_worker_fork`**:
   - This hook runs before forking workers and is where you call `GRPC.prefork`.
   - In preloading setups (default in Puma v7), it runs in the **master process** before workers are forked, as the application is preloaded in the master process.
   - Without preloading, it still runs in the **master process** before forking workers, but the application is not preloaded.
@@ -55,7 +55,7 @@ Puma's hooks determine when to call gRPC's lifecycle methods. Each hook plays a
   - This hook always runs in the **master process** after a worker is forked, regardless of whether preloading is enabled.
   - Call `GRPC.postfork_parent` here to finalize the master process's state after forking.
 
-- **`on_worker_boot`**:
+- **`before_worker_boot`**:
   - This hook always runs in the **worker process** after it is forked, regardless of whether preloading is enabled.
   - Call `GRPC.postfork_child` here to finalize the worker's state.
 

data/lib/puma/binder.rb

@@ -90,7 +90,7 @@ module Puma
     # @version 5.0.0
     #
     def create_activated_fds(env_hash)
-      @log_writer.debug "ENV['LISTEN_FDS'] #{@env['LISTEN_FDS'].inspect}  env_hash['LISTEN_PID'] #{env_hash['LISTEN_PID'].inspect}"
+      @log_writer.debug { "ENV['LISTEN_FDS'] #{@env['LISTEN_FDS'].inspect}  env_hash['LISTEN_PID'] #{env_hash['LISTEN_PID'].inspect}" }
       return [] unless env_hash['LISTEN_FDS'] && env_hash['LISTEN_PID'].to_i == $$
       env_hash['LISTEN_FDS'].to_i.times do |index|
         sock = TCPServer.for_fd(socket_activation_fd(index))
@@ -102,7 +102,7 @@ module Puma
           [:tcp, addr, port]
         end
         @activated_sockets[key] = sock
-        @log_writer.debug "Registered #{key.join ':'} for activation from LISTEN_FDS"
+        @log_writer.debug { "Registered #{key.join ':'} for activation from LISTEN_FDS" }
       end
       ["LISTEN_FDS", "LISTEN_PID"] # Signal to remove these keys from ENV
     end

data/lib/puma/configuration.rb

@@ -344,7 +344,7 @@ module Puma
     # @param arg [Launcher, Int] `:before_restart` passes Launcher
     #
     def run_hooks(key, arg, log_writer, hook_data = nil)
-      log_writer.debug "Running #{key} hooks"
+      log_writer.debug { "Running #{key} hooks" }
 
       options.all_of(key).each do |hook_options|
         begin

data/lib/puma/const.rb

@@ -100,7 +100,7 @@ module Puma
   # too taxing on performance.
   module Const
 
-    PUMA_VERSION = VERSION = "8.0.0"
+    PUMA_VERSION = VERSION = "8.0.1"
     CODE_NAME = "Into the Arena"
 
     PUMA_SERVER_STRING = ["puma", PUMA_VERSION, CODE_NAME].join(" ").freeze

data/lib/puma/launcher/bundle_pruner.rb

@@ -28,14 +28,12 @@ module Puma
 
         log '* Pruning Bundler environment'
         home = ENV['GEM_HOME']
-        bundle_gemfile = Bundler.original_env['BUNDLE_GEMFILE']
-        bundle_app_config = Bundler.original_env['BUNDLE_APP_CONFIG']
+        original_bundle_env = Bundler.original_env.select { |k, v| k.start_with?('BUNDLE_') && v }
 
         with_unbundled_env do
           ENV['GEM_HOME'] = home
-          ENV['BUNDLE_GEMFILE'] = bundle_gemfile
           ENV['PUMA_BUNDLER_PRUNED'] = '1'
-          ENV["BUNDLE_APP_CONFIG"] = bundle_app_config
+          original_bundle_env.each { |k, v| ENV[k] = v }
           args = [Gem.ruby, puma_wild_path, '-I', dirs.join(':')] + @original_argv
           # Defaults to true which breaks socket activation
           args += [{:close_others => false}]

data/lib/puma/log_writer.rb

@@ -90,8 +90,14 @@ module Puma
       @debug
     end
 
-    def debug(str)
-      log("% #{str}") if @debug
+    def debug(str=nil, &block)
+      if @debug
+        if block_given?
+          log("% #{yield}")
+        else
+          log("% #{str}")
+        end
+      end
     end
 
     # Write +str+ to +@stderr+

data/lib/puma/server.rb

@@ -417,7 +417,7 @@ module Puma
           end
         end
 
-        @log_writer.debug "Drained #{drain} additional connections." if drain
+        @log_writer.debug { "Drained #{drain} additional connections." } if drain
         @events.fire :state, @status
 
         if queue_requests

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: puma
 version: !ruby/object:Gem::Version
-  version: 8.0.0
+  version: 8.0.1
 platform: ruby
 authors:
 - Evan Phoenix