Bump puma from 3.12.1 to 5.6.9 in /2.5/test/puma-test-app
[!WARNING] Dependabot will stop supporting
bundler v1!Please upgrade to version
v2.
Bumps puma from 3.12.1 to 5.6.9.
Release notes
Sourced from puma's releases.
5.6.7
Security Address HTTP request smuggling vulnerabilities with zero-length Content Length header and trailer fields (GHSA-68xg-gqqm-vgj8)
5.6.5 / 2022-08-23
- Bugfixes
- NullIO#closed should return false (#2883)
- Puma::ControlCLI - allow refork command to be sent as a request (#2868, #2866)
- [jruby] Fix TLS verification hang (#2890, #2729)
- extconf.rb - don't use pkg_config('openssl') if '--with-openssl-dir' is used (#2885, #2839)
- MiniSSL - detect SSL_CTX_set_dh_auto (#2864, #2863)
- Fix rack.after_reply exceptions breaking connections (#2861, #2856)
- Escape SSL cert and filenames (#2855)
- Fail hard if SSL certs or keys are invalid (#2848)
- Fail hard if SSL certs or keys cannot be read by user (#2847)
- Fix build with Opaque DH in LibreSSL 3.5. (#2838)
- Pre-existing socket file removed when TERM is issued after USR2 (if puma is running in cluster mode) (#2817)
- Fix Puma::StateFile#load incompatibility (#2810)
5.6.4
- Security
- Close several HTTP Request Smuggling exploits (CVE-2022-24790)
The 5.6.3 release was a mistake (released the wrong branch), 5.6.4 is correct.
5.6.2 / 2022-02-11
- Bugfix/Security
- Response body will always be
closed. (GHSA-rmj8-8hhh-gv5h, related to #2809)5.6.1
Bugfixes
- Reverted a commit which appeared to be causing occasional blank header values (see issue #2808) (#2809)
Full Changelog: https://github.com/puma/puma/compare/v5.6.0...v5.6.1
5.6.0 - Birdie's Version
Maintainer
@nateberkopechad a daughter, nicknamed Birdie:
5.6.0 / 2022-01-25
- Features
- Support
localhostintegration inssl_bind(#2764, #2708)- Allow backlog parameter to be set with ssl_bind DSL (#2780)
- Remove yaml (psych) requirement in StateFile (#2784)
- Allow culling of oldest workers, previously was only youngest (#2773, #2794)
- Add worker_check_interval configuration option (#2759)
... (truncated)
Changelog
Sourced from puma's changelog.
5.6.9 / 2024-09-19
- Security
- Discards any headers using underscores if the non-underscore version also exists. Without this, an attacker could overwrite values set by intermediate proxies (e.g. X-Forwarded-For). (CVE-2024-45614/GHSA-9hf4-67fc-4vf4)
5.6.8 / 2024-01-08
- Security
- Limit the size of chunk extensions. Without this limit, an attacker could cause unbounded resource (CPU, network bandwidth) consumption. (GHSA-c2f4-cvqm-65w2)
5.6.7 / 2023-08-18
- Security
- Address HTTP request smuggling vulnerabilities with zero-length Content Length header and trailer fields (GHSA-68xg-gqqm-vgj8)
5.6.6 / 2023-06-21
- Bugfix
- Prevent loading with rack 3 (#3166)
5.6.5 / 2022-08-23
Feature
Bugfixes
- NullIO#closed should return false (#2883)
- [jruby] Fix TLS verification hang (#2890, #2729)
- extconf.rb - don't use pkg_config('openssl') if '--with-openssl-dir' is used (#2885, #2839)
- MiniSSL - detect SSL_CTX_set_dh_auto (#2864, #2863)
- Fix rack.after_reply exceptions breaking connections (#2861, #2856)
- Escape SSL cert and filenames (#2855)
- Fail hard if SSL certs or keys are invalid (#2848)
- Fail hard if SSL certs or keys cannot be read by user (#2847)
- Fix build with Opaque DH in LibreSSL 3.5. (#2838)
- Pre-existing socket file removed when TERM is issued after USR2 (if puma is running in cluster mode) (#2817)
- Fix Puma::StateFile#load incompatibility (#2810)
5.6.4 / 2022-03-30
- Security
- Close several HTTP Request Smuggling exploits (CVE-2022-24790)
5.6.2 / 2022-02-11
- Bugfix/Security
- Response body will always be
closed. (GHSA-rmj8-8hhh-gv5h, related to #2809)5.6.1 / 2022-01-26
... (truncated)
Commits
f196b23Merge commit from fork24eec195.6.93c8e8b05.6.9 release note [ci skip]12935735.6.8bbb880fMerge pull request from GHSA-c2f4-cvqm-65w278393bf5.6.77405a21Merge pull request from GHSA-68xg-gqqm-vgj8d33424b5.6.7 release note [ci skip]f8c7b235.6.608af1b55.6.6 release note- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
Pull Request validation
Failed
🔴 Review - Missing review from a member (2 required)
Success
🟢 CI - All checks have passed
Closing this pull request. we do not plan to bump app
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
