puma/puma
A Ruby/Rack web server built for parallelism
Release date:
September 23, 2019
Previous version:
v4.1.1
(released September 9, 2019)
Magnitude:
3,786
Diff Delta
Contributors:
12 total committers
Commits:
40 Features Released with v4.2.0
Browse Other Releases
Latest Pending
Unreleased 😎
v4.3.2
Released February 27, 2020
3 Δ
v4.3.1
Released December 5, 2019
62 Δ
v4.3.0
Released November 7, 2019
2,841 Δ
v4.2.1
Released October 7, 2019
302 Δ
v4.2.0
Released September 23, 2019
3,786 Δ
v4.1.1
Released September 9, 2019
267 Δ
v4.1.0
Released August 8, 2019
2,272 Δ
v4.0.1
Released July 11, 2019
127 Δ
v4.0.0
Released May 21, 2020
415 Δ
v3.12.6
Released May 21, 2020
59 Δ
Top Contributors in v4.2.0
MSP-Greg
nateberkopec
daveallie
evanphx
dentarg
olleolleolle
david-costa-9d3a
sj26
lmansur
PericlesTheo
Directory Browser for v4.2.0
We haven't yet finished calculating and confirming the files and directories changed in this release. Please check back soon.
Release Notes Published
- 6 features
- Pumactl has a new -e environment option and reads config/puma/<environment>.rb config files (#1885)
- Semicolons are now allowed in URL paths (MRI only), useful for Angular or Redmine (#1934)
- Allow extra dependencies to be defined when using prune_bundler (#1105)
- Puma now reports the correct port when binding to port 0, also reports other listeners when binding to localhost (#1786)
- Sending SIGINFO to any Puma worker now prints currently active threads and their backtraces (#1320)
- Puma threads all now have their name set on Ruby 2.3+ (#1968)
- 4 bugfixes
- Fix some misbehavior with phased restart and externally SIGTERMed workers (#1908, #1952)
- Fix socket closing on error (#1941)
- Removed unnecessary SIGINT trap for JRuby that caused some race conditions (#1961)
- Fix socket files being left around after process stopped (#1970)
- Absolutely thousands of lines of test improvements and fixes thanks to @MSP-Greg
