🚨 [security] Update rubocop: 0.52.1 → 1.11.0 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ rubocop (0.52.1 → 1.11.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

✳️ capybara (3.10.0 → 3.35.3) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ addressable (indirect, 2.5.2 → 2.7.0) · Repo · Changelog

Release Notes

2.7.0 (from changelog)

• added :compacted flag to normalized_query
• heuristic_parse handles mailto: more intuitively
• refactored validation to use a prepended module
• dropped explicit support for JRuby 9.0.5.0
• compatibility w/ public_suffix 4.x
• performance improvements

2.6.0 (from changelog)

• added tld= method to allow assignment to the public suffix
• most heuristic_parse patterns are now case-insensitive
• heuristic_parse handles more file:// URI variations
• fixes bug in heuristic_parse when uri starts with digit
• fixes bug in request_uri= with query strings
• fixes template issues with nil and ? operator
• frozen_string_literal pragmas added
• minor performance improvements in regexps
• fixes to eliminate warnings

Does any of this look wrong? Please let us know.

↗️ ast (indirect, 2.4.0 → 2.4.2) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mini_mime (indirect, 1.0.1 → 1.0.2) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mini_portile2 (indirect, 2.3.0 → 2.5.0) · Repo · Changelog

Release Notes

2.5.0

2.5.0 / 2020-02-24

Enhancements

• When verifying GPG signatures, remove all imported pubkeys from keyring [#90] (Thanks, @hanazuki!)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ nokogiri (indirect, 1.8.5 → 1.11.1) · Repo · Changelog

Security Advisories 🚨

🚨 Nokogiri::XML::Schema trusts input by default, exposing risk of an XXE vulnerability

Description

In Nokogiri versions <= 1.11.0.rc3, XML Schemas parsed by Nokogiri::XML::Schema
are trusted by default, allowing external resources to be accessed over the
network, potentially enabling XXE or SSRF attacks.

This behavior is counter to
the security policy followed by Nokogiri maintainers, which is to treat all input
as untrusted by default whenever possible.

Please note that this security
fix was pushed into a new minor version, 1.11.x, rather than a patch release to
the 1.10.x branch, because it is a breaking change for some schemas and the risk
was assessed to be "Low Severity".

Affected Versions

Nokogiri <= 1.10.10 as well as prereleases 1.11.0.rc1, 1.11.0.rc2, and 1.11.0.rc3

Mitigation

There are no known workarounds for affected versions. Upgrade to Nokogiri
1.11.0.rc4 or later.

If, after upgrading to 1.11.0.rc4 or later, you wish
to re-enable network access for resolution of external resources (i.e., return to
the previous behavior):

1. Ensure the input is trusted. Do not enable this option
   for untrusted input.
2. When invoking the Nokogiri::XML::Schema constructor,
   pass as the second parameter an instance of Nokogiri::XML::ParseOptions with the
   NONET flag turned off.

So if your previous code was:

# in v1.11.0.rc3 and earlier, this call allows resources to be accessed over the network
# but in v1.11.0.rc4 and later, this call will disallow network access for external resources
schema = Nokogiri::XML::Schema.new(schema)
# in v1.11.0.rc4 and later, the following is equivalent to the code above

# (the second parameter is optional, and this demonstrates its default value)

schema = Nokogiri::XML::Schema.new(schema, Nokogiri::XML::ParseOptions::DEFAULT_SCHEMA)

Then you can add the second parameter to indicate that the input is trusted by changing it to:

# in v1.11.0.rc3 and earlier, this would raise an ArgumentError
# but in v1.11.0.rc4 and later, this allows resources to be accessed over the network
schema = Nokogiri::XML::Schema.new(trusted_schema, Nokogiri::XML::ParseOptions.new.nononet)

🚨 xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.

Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in #1992. Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.

🚨 Nokogiri gem, via libxslt, is affected by multiple vulnerabilities

Nokogiri v1.10.5 has been released.

This is a security release. It addresses three CVEs in upstream libxml2,
for which details are below.

If you're using your distro's system libraries, rather than Nokogiri's
vendored libraries, there's no security need to upgrade at this time,
though you may want to check with your distro whether they've patched this
(Canonical has patched Ubuntu packages). Note that libxslt 1.1.34 addresses
these vulnerabilities.

Full details about the security update are available in Github Issue
[#1943] #1943.

---

CVE-2019-13117

https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-13117.html

Priority: Low

Description: In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings
could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This
could allow an attacker to discern whether a byte on the stack contains the
characters A, a, I, i, or 0, or any other character.

Patched with commit https://gitlab.gnome.org/GNOME/libxslt/commit/c5eb6cf3aba0af048596106ed839b4ae17ecbcb1

---

CVE-2019-13118

https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-13118.html

Priority: Low

Description: In numbers.c in libxslt 1.1.33, a type holding grouping characters of an
xsl:number instruction was too narrow and an invalid character/length
combination could be passed to xsltNumberFormatDecimal, leading to a read
of uninitialized stack data

Patched with commit https://gitlab.gnome.org/GNOME/libxslt/commit/6ce8de69330783977dd14f6569419489875fb71b

---

CVE-2019-18197

https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-18197.html

Priority: Medium

Description: In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't
reset under certain circumstances. If the relevant memory area happened to
be freed and reused in a certain way, a bounds check could fail and memory
outside a buffer could be written to, or uninitialized data could be
disclosed.

Patched with commit https://gitlab.gnome.org/GNOME/libxslt/commit/2232473733b7313d67de8836ea3b29eec6e8e285

🚨 Nokogiri Command Injection Vulnerability

🚨 Nokogiri gem, via libxslt, is affected by improper access control vulnerability

Nokogiri v1.10.3 has been released.

This is a security release. It addresses a CVE in upstream libxslt rated as
"Priority: medium" by Canonical, and "NVD Severity: high" by Debian. More
details are available below.

If you're using your distro's system libraries, rather than Nokogiri's
vendored libraries, there's no security need to upgrade at this time, though
you may want to check with your distro whether they've patched this
(Canonical has patched Ubuntu packages). Note that this patch is not yet (as
of 2019-04-22) in an upstream release of libxslt.

Full details about the security update are available in Github Issue
[#1892] #1892.

---

CVE-2019-11068

Permalinks are:

• Canonical: https://people.canonical.com/~ubuntu-security/cve/CVE-2019-11068
• Debian: https://security-tracker.debian.org/tracker/CVE-2019-11068

Description:

libxslt through 1.1.33 allows bypass of a protection mechanism
because callers of xsltCheckRead and xsltCheckWrite permit access
even upon receiving a -1 error code. xsltCheckRead can return -1 for
a crafted URL that is not actually invalid and is subsequently
loaded.

Canonical rates this as "Priority: Medium".

Debian rates this as "NVD Severity: High (attack range: remote)".

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ parallel (indirect, 1.12.1 → 1.20.1) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ parser (indirect, 2.5.0.0 → 3.0.0.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ public_suffix (indirect, 3.0.3 → 4.0.6) · Repo · Changelog

Release Notes

4.0.6 (from changelog)

Changed

• Updated definitions.

4.0.5 (from changelog)

Changed

• Updated definitions.

4.0.4 (from changelog)

Changed

• Updated definitions.

4.0.3 (from changelog)

Fixed

• Fixed 2.7 deprecations and warnings (GH-167). [Thanks @BrianHawley]

4.0.2 (from changelog)

Changed

• Updated definitions.

4.0.1 (from changelog)

• CHANGED: Updated definitions.

4.0.0 (from changelog)

• CHANGED: Minimum Ruby version is 2.3

3.1.1 (from changelog)

• CHANGED: Updated definitions.
• CHANGED: Rolled back support for Ruby 2.3 (GH-161, GH-162)

IMPORTANT: 3.x is the latest version compatible with Ruby 2.1 and Ruby 2.2.

3.1.0 (from changelog)

• CHANGED: Updated definitions.
• CHANGED: Minimum Ruby version is 2.3
• CHANGED: Upgraded to Bundler 2.x

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ rack (indirect, 2.0.5 → 2.2.3) · Repo · Changelog

Security Advisories 🚨

🚨 Percent-encoded cookies can be used to overwrite existing prefixed cookie names

It is possible to forge a secure or host-only cookie prefix in Rack using
an arbitrary cookie write by using URL encoding (percent-encoding) on the
name of the cookie. This could result in an application that is dependent on
this prefix to determine if a cookie is safe to process being manipulated
into processing an insecure or cross-origin request.
This vulnerability has been assigned the CVE identifier CVE-2020-8184.

Versions Affected: rack < 2.2.3, rack < 2.1.4
Not affected: Applications which do not rely on __Host- and __Secure- prefixes to determine if a cookie is safe to process
Fixed Versions: rack >= 2.2.3, rack >= 2.1.4

Impact

An attacker may be able to trick a vulnerable application into processing an
insecure (non-SSL) or cross-origin request if they can gain the ability to write
arbitrary cookies that are sent to the application.

Workarounds

If your application is impacted but you cannot upgrade to the released versions or apply
the provided patch, this issue can be temporarily addressed by adding the following workaround:

module Rack
  module Utils
    module_function def parse_cookies_header(header)
      return {} unless header
      header.split(/[;] */n).each_with_object({}) do |cookie, cookies|
        next if cookie.empty?
        key, value = cookie.split('=', 2)
        cookies[key] = (unescape(value) rescue value) unless cookies.key?(key)
      end
    end
  end
end

🚨 Percent-encoded cookies can be used to overwrite existing prefixed cookie names

It is possible to forge a secure or host-only cookie prefix in Rack using
an arbitrary cookie write by using URL encoding (percent-encoding) on the
name of the cookie. This could result in an application that is dependent on
this prefix to determine if a cookie is safe to process being manipulated
into processing an insecure or cross-origin request.
This vulnerability has been assigned the CVE identifier CVE-2020-8184.

Versions Affected: rack < 2.2.3, rack < 2.1.4
Not affected: Applications which do not rely on __Host- and __Secure- prefixes to determine if a cookie is safe to process
Fixed Versions: rack >= 2.2.3, rack >= 2.1.4

Impact

An attacker may be able to trick a vulnerable application into processing an
insecure (non-SSL) or cross-origin request if they can gain the ability to write
arbitrary cookies that are sent to the application.

Workarounds

If your application is impacted but you cannot upgrade to the released versions or apply
the provided patch, this issue can be temporarily addressed by adding the following workaround:

module Rack
  module Utils
    module_function def parse_cookies_header(header)
      return {} unless header
      header.split(/[;] */n).each_with_object({}) do |cookie, cookies|
        next if cookie.empty?
        key, value = cookie.split('=', 2)
        cookies[key] = (unescape(value) rescue value) unless cookies.key?(key)
      end
    end
  end
end

🚨 Directory traversal in Rack::Directory app bundled with Rack

There was a possible directory traversal vulnerability in the Rack::Directory app
that is bundled with Rack.

Versions Affected: rack < 2.2.0
Not affected: Applications that do not use Rack::Directory.
Fixed Versions: 2.1.3, >= 2.2.0

Impact

If certain directories exist in a director that is managed by
Rack::Directory, an attacker could, using this vulnerability, read the
contents of files on the server that were outside of the root specified in the
Rack::Directory initializer.

Workarounds

Until such time as the patch is applied or their Rack version is upgraded,
we recommend that developers do not use Rack::Directory in their
applications.

🚨 Directory traversal in Rack::Directory app bundled with Rack

There was a possible directory traversal vulnerability in the Rack::Directory app
that is bundled with Rack.

Versions Affected: rack < 2.2.0
Not affected: Applications that do not use Rack::Directory.
Fixed Versions: 2.1.3, >= 2.2.0

Impact

If certain directories exist in a director that is managed by
Rack::Directory, an attacker could, using this vulnerability, read the
contents of files on the server that were outside of the root specified in the
Rack::Directory initializer.

Workarounds

Until such time as the patch is applied or their Rack version is upgraded,
we recommend that developers do not use Rack::Directory in their
applications.

🚨 Possible information leak / session hijack vulnerability

There's a possible information leak / session hijack vulnerability in Rack.

Attackers may be able to find and hijack sessions by using timing attacks
targeting the session id. Session ids are usually stored and indexed in a
database that uses some kind of scheme for speeding up lookups of that
session id. By carefully measuring the amount of time it takes to look up
a session, an attacker may be able to find a valid session id and hijack
the session.

The session id itself may be generated randomly, but the way the session is
indexed by the backing store does not use a secure comparison.

Impact:

The session id stored in a cookie is the same id that is used when querying
the backing session storage engine. Most storage mechanisms (for example a
database) use some sort of indexing in order to speed up the lookup of that
id. By carefully timing requests and session lookup failures, an attacker
may be able to perform a timing attack to determine an existing session id
and hijack that session.

🚨 Possible DoS vulnerability in Rack

There is a possible DoS vulnerability in the multipart parser in Rack. This
vulnerability has been assigned the CVE identifier CVE-2018-16470.

Versions Affected: 2.0.4, 2.0.5
Not affected: <= 2.0.3
Fixed Versions: 2.0.6

Impact

There is a possible DoS vulnerability in the multipart parser in Rack.
Carefully crafted requests can cause the multipart parser to enter a
pathological state, causing the parser to use CPU resources disproportionate to
the request size.

Impacted code can look something like this:

Rack::Request.new(env).params

But any code that uses the multi-part parser may be vulnerable.

Rack users that have manually adjusted the buffer size in the multipart parser
may be vulnerable as well.

All users running an affected release should either upgrade or use one of the
workarounds immediately.

Releases

The 2.0.6 release is available at the normal locations.

Workarounds

To work around this issue, the following code can be used:

require "rack/multipart/parser"
Rack::Multipart::Parser.send :remove_const, :BUFSIZE

Rack::Multipart::Parser.const_set :BUFSIZE, 16384

🚨 Possible XSS vulnerability in Rack

There is a possible vulnerability in Rack. This vulnerability has been
assigned the CVE identifier CVE-2018-16471.

Versions Affected: All.
Not affected: None.
Fixed Versions: 2.0.6, 1.6.11

Impact

There is a possible XSS vulnerability in Rack. Carefully crafted requests can
impact the data returned by the scheme method on Rack::Request.
Applications that expect the scheme to be limited to "http" or "https" and do
not escape the return value could be vulnerable to an XSS attack.

Vulnerable code looks something like this:

<%= request.scheme.html_safe %>

Note that applications using the normal escaping mechanisms provided by Rails
may not impacted, but applications that bypass the escaping mechanisms, or do
not use them may be vulnerable.

All users running an affected release should either upgrade or use one of the
workarounds immediately.

Releases

The 2.0.6 and 1.6.11 releases are available at the normal locations.

Workarounds

The following monkey patch can be applied to work around this issue:

require "rack"
require "rack/request"
class Rack::Request

SCHEME_WHITELIST = %w(https http).freeze
def scheme

if get_header(Rack::HTTPS) == 'on'

'https'

elsif get_header(HTTP_X_FORWARDED_SSL) == 'on'

'https'

elsif forwarded_scheme

forwarded_scheme

else

get_header(Rack::RACK_URL_SCHEME)

end

end
def forwarded_scheme

scheme_headers = [

get_header(HTTP_X_FORWARDED_SCHEME),

get_header(HTTP_X_FORWARDED_PROTO).to_s.split(',')[0]

]
scheme_headers.each do |header|

return header if SCHEME_WHITELIST.include?(header)

end
nil

end

end

Release Notes

2.2.2 (from changelog)

Fixed

• Fix incorrect Rack::Request#host value. (#1591, @ioquatix)
• Revert Rack::Handler::Thin implementation. (#1583, @jeremyevans)
• Double assignment is still needed to prevent an "unused variable" warning. (#1589, @kamipo)
• Fix to handle same_site option for session pool. (#1587, @kamipo)

2.2.1 (from changelog)

Fixed

• Rework Rack::Request#ip to handle empty forwarded_for. (#1577, @ioquatix)

2.2.0 (from changelog)

SPEC Changes

• rack.session request environment entry must respond to to_hash and return unfrozen Hash. (@jeremyevans)
• Request environment cannot be frozen. (@jeremyevans)
• CGI values in the request environment with non-ASCII characters must use ASCII-8BIT encoding. (@jeremyevans)
• Improve SPEC/lint relating to SERVER_NAME, SERVER_PORT and HTTP_HOST. (#1561, @ioquatix)

Added

• rackup supports multiple -r options and will require all arguments. (@jeremyevans)
• Server supports an array of paths to require for the :require option. (@khotta)
• Files supports multipart range requests. (@fatkodima)
• Multipart::UploadedFile supports an IO-like object instead of using the filesystem, using :filename and :io options. (@jeremyevans)
• Multipart::UploadedFile supports keyword arguments :path, :content_type, and :binary in addition to positional arguments. (@jeremyevans)
• Static supports a :cascade option for calling the app if there is no matching file. (@jeremyevans)
• Session::Abstract::SessionHash#dig. (@jeremyevans)
• Response.[] and MockResponse.[] for creating instances using status, headers, and body. (@ioquatix)
• Convenient cache and content type methods for Rack::Response. (#1555, @ioquatix)

Changed

• Request#params no longer rescues EOFError. (@jeremyevans)
• Directory uses a streaming approach, significantly improving time to first byte for large directories. (@jeremyevans)
• Directory no longer includes a Parent directory link in the root directory index. (@jeremyevans)
• QueryParser#parse_nested_query uses original backtrace when reraising exception with new class. (@jeremyevans)
• ConditionalGet follows RFC 7232 precedence if both If-None-Match and If-Modified-Since headers are provided. (@jeremyevans)
• .ru files supports the frozen-string-literal magic comment. (@eregon)
• Rely on autoload to load constants instead of requiring internal files, make sure to require 'rack' and not just 'rack/...'. (@jeremyevans)
• Etag will continue sending ETag even if the response should not be cached. (@henm)
• Request#host_with_port no longer includes a colon for a missing or empty port. (@AlexWayfer)
• All handlers uses keywords arguments instead of an options hash argument. (@ioquatix)
• Files handling of range requests no longer return a body that supports to_path, to ensure range requests are handled correctly. (@jeremyevans)
• Multipart::Generator only includes Content-Length for files with paths, and Content-Disposition filename if the UploadedFile instance has one. (@jeremyevans)
• Request#ssl? is true for the wss scheme (secure websockets). (@jeremyevans)
• Rack::HeaderHash is memoized by default. (#1549, @ioquatix)
• Rack::Directory allow directory traversal inside root directory. (#1417, @ThomasSevestre)
• Sort encodings by server preference. (#1184, @ioquatix, @wjordan)
• Rework host/hostname/authority implementation in Rack::Request. #host and #host_with_port have been changed to correctly return IPv6 addresses formatted with square brackets, as defined by RFC3986. (#1561, @ioquatix)
• Rack::Builder parsing options on first #\ line is deprecated. (#1574, @ioquatix)

Removed

• Directory#path as it was not used and always returned nil. (@jeremyevans)
• BodyProxy#each as it was only needed to work around a bug in Ruby <1.9.3. (@jeremyevans)
• URLMap::INFINITY and URLMap::NEGATIVE_INFINITY, in favor of Float::INFINITY. (@ch1c0t)
• Deprecation of Rack::File. It will be deprecated again in rack 2.2 or 3.0. (@rafaelfranca)
• Support for Ruby 2.2 as it is well past EOL. (@ioquatix)
• Remove Rack::Files#response_body as the implementation was broken. (#1153, @ioquatix)
• Remove SERVER_ADDR which was never part of the original SPEC. (#1573, @ioquatix)

Fixed

• Directory correctly handles root paths containing glob metacharacters. (@jeremyevans)
• Cascade uses a new response object for each call if initialized with no apps. (@jeremyevans)
• BodyProxy correctly delegates keyword arguments to the body object on Ruby 2.7+. (@jeremyevans)
• BodyProxy#method correctly handles methods delegated to the body object. (@jeremyevans)
• Request#host and Request#host_with_port handle IPv6 addresses correctly. (@AlexWayfer)
• Lint checks when response hijacking that rack.hijack is called with a valid object. (@jeremyevans)
• Response#write correctly updates Content-Length if initialized with a body. (@jeremyevans)
• CommonLogger includes SCRIPT_NAME when logging. (@Erol)
• Utils.parse_nested_query correctly handles empty queries, using an empty instance of the params class instead of a hash. (@jeremyevans)
• Directory correctly escapes paths in links. (@yous)
• Request#delete_cookie and related Utils methods handle :domain and :path options in same call. (@jeremyevans)
• Request#delete_cookie and related Utils methods do an exact match on :domain and :path options. (@jeremyevans)
• Static no longer adds headers when a gzipped file request has a 304 response. (@chooh)
• ContentLength sets Content-Length response header even for bodies not responding to to_ary. (@jeremyevans)
• Thin handler supports options passed directly to Thin::Controllers::Controller. (@jeremyevans)
• WEBrick handler no longer ignores :BindAddress option. (@jeremyevans)
• ShowExceptions handles invalid POST data. (@jeremyevans)
• Basic authentication requires a password, even if the password is empty. (@jeremyevans)
• Lint checks response is array with 3 elements, per SPEC. (@jeremyevans)
• Support for using :SSLEnable option when using WEBrick handler. (Gregor Melhorn)
• Close response body after buffering it when buffering. (@ioquatix)
• Only accept ; as delimiter when parsing cookies. (@mrageh)
• Utils::HeaderHash#clear clears the name mapping as well. (@raxoft)
• Support for passing nil Rack::Files.new, which notably fixes Rails' current ActiveStorage::FileServer implementation. (@ioquatix)

Documentation

• CHANGELOG updates. (@aupajo)
• Added CONTRIBUTING. (@dblock)

2.1.2 (from changelog)

• Fix multipart parser for some files to prevent denial of service (@aiomaster)
• Fix Rack::Builder#use with keyword arguments (@kamipo)
• Skip deflating in Rack::Deflater if Content-Length is 0 (@jeremyevans)
• Remove SessionHash#transform_keys, no longer needed (@pavel)
• Add to_hash to wrap Hash and Session classes (@oleh-demyanyuk)
• Handle case where session id key is requested but missing (@jeremyevans)

2.1.1 (from changelog)

• Remove Rack::Chunked from Rack::Server default middleware. (#1475, @ioquatix)
• Restore support for code relying on SessionId#to_s. (@jeremyevans)

2.1.0 (from changelog)

Added

• Add support for SameSite=None cookie value. (@hennikul)
• Add trailer headers. (@eileencodes)
• Add MIME Types for video streaming. (@styd)
• Add MIME Type for WASM. (@buildrtech)
• Add Early Hints(103) to status codes. (@egtra)
• Add Too Early(425) to status codes. (@y-yagi)
• Add Bandwidth Limit Exceeded(509) to status codes. (@CJKinni)
• Add method for custom ip_filter. (@svcastaneda)
• Add boot-time profiling capabilities to rackup. (@tenderlove)
• Add multi mapping support for X-Accel-Mappings header. (@yoshuki)
• Add sync: false option to Rack::Deflater. (Eric Wong)
• Add Builder#freeze_app to freeze application and all middleware instances. (@jeremyevans)
• Add API to extract cookies from Rack::MockResponse. (@petercline)

Changed

• Don't propagate nil values from middleware. (@ioquatix)
• Lazily initialize the response body and only buffer it if required. (@ioquatix)
• Fix deflater zlib buffer errors on empty body part. (@felixbuenemann)
• Set X-Accel-Redirect to percent-encoded path. (@diskkid)
• Remove unnecessary buffer growing when parsing multipart. (@tainoe)
• Expand the root path in Rack::Static upon initialization. (@rosenfeld)
• Make ShowExceptions work with binary data. (@axyjo)
• Use buffer string when parsing multipart requests. (@janko-m)
• Support optional UTF-8 Byte Order Mark (BOM) in config.ru. (@mikegee)
• Handle X-Forwarded-For with optional port. (@dpritchett)
• Use Time#httpdate format for Expires, as proposed by RFC 7231. (@nanaya)
• Make Utils.status_code raise an error when the status symbol is invalid instead of 500. (@adambutler)
• Rename Request::SCHEME_WHITELIST to Request::ALLOWED_SCHEMES.
• Make Multipart::Parser.get_filename accept files with + in their name. (@lucaskanashiro)
• Add Falcon to the default handler fallbacks. (@ioquatix)
• Update codebase to avoid string mutations in preparation for frozen_string_literals. (@pat)
• Change MockRequest#env_for to rely on the input optionally responding to #size instead of #length. (@janko)
• Rename Rack::File -> Rack::Files and add deprecation notice. (@postmodern).
• Prefer Base64 “strict encoding” for Base64 cookies. (@ioquatix)

Removed

• Remove to_ary from Response (@tenderlove)
• Deprecate Rack::Session::Memcache in favor of Rack::Session::Dalli from dalli gem (@fatkodima)

Fixed

• Eliminate warnings for Ruby 2.7. (@osamtimizer)

Documentation

• Update broken example in Session::Abstract::ID documentation. (tonytonyjan)
• Add Padrino to the list of frameworks implmenting Rack. (@wikimatze)
• Remove Mongrel from the suggested server options in the help output. (@tricknotes)
• Replace HISTORY.md and NEWS.md with CHANGELOG.md. (@twitnithegirl)
• CHANGELOG updates. (@drenmi, @p8)

2.0.8 (from changelog)

• [CVE-2019-16782] Prevent timing attacks targeted at session ID lookup. (@tenderlove, @rafaelfranca)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ regexp_parser (indirect, 1.2.0 → 2.1.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ ruby-progressbar (indirect, 1.10.0 → 1.11.0) · Repo · Changelog

Release Notes

1.11.0 (from changelog)

Add

• RUBY_PROGRESS_BAR_FORMAT Environment Variable

Merge

• PR #165 - Show Unknown Time Remaining After Timer Reset

Fix

• Show Unknown Time Remaining After Bar Is Reset

Uncategorized

• Merge PR #167 - Convert To Github Actions

1.10.1 (from changelog)

Change

• Make Extra Sure We're Not Loading Ruby's Time Class

Fix

• CHANGELOG URI in both gemspecs to point to master CHANGELOG.md
• Ruby 1.8/1.9 IO Doesn't Respond to winsize

Remove

• allowed_push_host From gemspecs

Does any of this look wrong? Please let us know.

↗️ unicode-display_width (indirect, 1.3.0 → 2.0.0) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 racc (added, 1.5.2)

🆕 rexml (added, 3.2.4)

🆕 rubocop-ast (added, 1.4.1)

🗑️ powerpack (removed)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[sourcelevel-bot]

SourceLevel has finished reviewing this Pull Request and has found:

• 45 possible new issues (including those that may have been commented here).
• 7 fixed issues! 🎉

See more details about this review.