Puma: v5.1.0 Release

Release date:
November 30, 2020
Previous version:
v5.0.4 (released October 27, 2020)
Magnitude:
1,254 Diff Delta
Contributors:
9 total committers
Data confidence:
Commits:

30 Features Released with v5.1.0

Top Contributors in v5.1.0

cjlarose
ekohl
nateberkopec
MSP-Greg
elct9620
dentarg
kuei0221
karloscodes
JuanitoFatas

Directory Browser for v5.1.0

We haven't yet finished calculating and confirming the files and directories changed in this release. Please check back soon.

Release Notes Published

5.1.0 / 2020-11-30

  • Features

    • Phased restart availability is now always logged, even if it is not available.
    • Prints the loaded configuration if the environment variable PUMA_LOG_CONFIG is present ([#2472])
    • Integrate with systemd's watchdog and notification features ([#2438])
    • Adds max_fast_inline as a configuration option for the Server object ([#2406])
    • You can now fork workers from worker 0 using SIGURG w/o fork_worker enabled [#2449]
    • Add option to bind to systemd activated sockets ([#2362])
    • Add compile option to change the QUERY_STRING max length ([#2485])
  • Bugfixes

    • Fix JRuby handling in Puma::DSL#ssl_bind ([#2489])
    • control_cli.rb - all normal output should be to @stdout ([#2487])
    • Catch 'Error in reactor loop escaped: mode not supported for this object: r' ([#2477])
    • Ignore Rails' reaper thread (and any thread marked forksafe) for warning ([#2475])
    • Ignore illegal (by Rack spec) response header ([#2439])
    • Close idle connections immediately on shutdown ([#2460])
    • Fix some instances of phased restart errors related to the json gem ([#2473])
    • Remove use of json gem to fix phased restart errors ([#2479])
    • Fix grouping regexp of ILLEGAL_HEADER_KEY_REGEX ([#2495])