search

Automattic / wpcom.ex

WordPress.com Elixir API client
https://hex.pm/packages/wpcom
MIT License
9 stars 2 forks source link

Bump bandit from 1.1.3 to 1.5.0 #115

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Bumps bandit from 1.1.3 to 1.5.0.

Changelog

Sourced from bandit's changelog.

1.5.0 (21 Apr 2024)

Enhancements

  • Bandit now respects an exception's conformance to Plug.Exception when determining which status code to return to the client (if the plug did not already send one). Previously they were always returned as 500 (for HTTP/1) or an 'internal error' stream error (for HTTP/2)
  • Bandit now only logs the stacktrace of plug-generated exceptions whose status code (as determined by Plug.Exception.status/1) is contained within the new log_exceptions_with_status_codes configuration option (defaulting to 500..599)
  • As a corollary to the above, Bandit request handler processes no longer exit abnormally in the case of plug-generated exceptions

Changes

  • HTTP semantic errors encountered in an HTTP/2 request are returned to the client using their proper status code instead of as a 'protocol error' stream error

1.4.2 (2 Apr 2024)

Enhancements

  • Support top-level :inet and :inet6 options for Plug.Cowboy compatibility (#337)

1.4.1 (27 Mar 2024)

Changes

  • BREAKING CHANGE Move log_protocol_errors configuration option into shared http_options top-level config (and apply it to HTTP/2 errors as well)
  • BREAKING CHANGE Remove origin_telemetry_span_context from WebSocket telemetry events
  • BREAKING CHANGE Remove stream_id from HTTP/2 telemetry events
  • Add conn to the metadata of telemetry start events for HTTP requests
  • Stop sending WebSocket upgrade failure reasons to the client (they're still logged)

Fixes

  • Return HTTP semantic errors to HTTP/2 clients as protocol errors instead of internal errors

1.4.0 (26 Mar 2024)

[!WARNING] IMPORTANT Phoenix users MUST upgrade to WebSockAdapter 0.5.6 or newer when upgrading to Bandit 1.4.0 or newer as some internal module names have changed

... (truncated)

Commits


Dependabot compatibility score

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 6 months ago

Superseded by #117.