Update plug_cowboy 2.5.2 → 2.7.4 (minor) #93
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
✳️ plug_cowboy (2.5.2 → 2.7.4) · Repo · Changelog
Release Notes
2.7.4 (from changelog)
2.7.3 (from changelog)
2.7.2 (from changelog)
2.7.1 (from changelog)
2.7.0 (from changelog)
2.6.2 (from changelog)
2.6.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 37 commits:
Release v2.7.4
Release v2.7.4
Ensure crash_reason is a two-element tuple for exit case (#108)
Update CI for additional task
Update CI (#109)
Use a fixed port on websocket tests
Fix warnings on more recent Elixir versions
Emit {:plug_conn, :sent} on responses
Release: v2.7.3
Translate errors for Cowboy 2.13.0
Improve docs (#104)
Release v2.7.2
Update ExDoc
Ranch translator: `crash_reason` should be a two-element tuple (#102)
Fix inform headers
Upgrade deps
Remove deprecated http2 push tests
Update obsolete links in the docs (#100)
Bump cowboy and cowlib (#99)
Release v2.7.1
Fix cookie handling in recent Cowboy versions
Release v2.7: do not allow Cowboy 2.11
Release v2.6.2
Fix calls to deprecated Logger.warn/2 (#94)
Release v2.6.1
Support leaner :check_interval option on drainer
Fix flaky translator test (#91)
mix format
Allow for opt-out of conn metadata on exception logs (#90)
Update ci.yml
Release v2.6.0
More fixes
Prepare for 2.6.0
Implement WebSocket support based on Plug.Conn.Adapter.upgrade/3 (#88)
Use erlef/setup-beam for GH action (#82)
Add 1.13 to CI matrix (#81)
Update ci.yml
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Sorry, we couldn't find anything useful about this release.
Release Notes
2.0.7 (from changelog)
2.0.6 (from changelog)
2.0.5 (from changelog)
2.0.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
Release v2.0.7
Fix extension name for jp2 (#85)
Update CI (#86)
CI housekeeping (#83)
Remove trailing whitespace
Release v2.0.6
Add `application/zstd` (Zstandard) (#82)
Add MIME type for APNG (#81)
Add MIME type for jp2000 files (#80)
Add known_types/0 function that lists all known types (#79)
Fix broken CI (#78)
Release v2.0.5
Allow conflicting extensions to be configured
Release v2.0.4
Release v2.0.4
ALlow suffixes to be customizable
Only return extensions for known structured syntax suffixes (#76)
Allow mimes to be fully overridden
Merge custom extensions without overriding the default ones (#73)
Release Notes
1.18.0 (from changelog)
1.17.0 (from changelog)
1.16.2 (from changelog)
1.16.1 (from changelog)
1.16.0 (from changelog)
1.15.3 (from changelog)
1.15.2 (from changelog)
1.15.1 (from changelog)
1.15.0 (from changelog)
1.14.2 (from changelog)
1.14.1 (from changelog)
1.14.0 (from changelog)
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.
Release Notes
1.2.5 (from changelog)
1.2.4 (from changelog)
1.2.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
Release v1.2.5
Release v1.2.5
Allow iodata in AAD
Improve tests with custom AAD (#34)
Release v1.2.4
Allow custom AAD to be provided to message encryptor (#33)
Rely more on iodata
Bump Elixir to test against to 14.2 (#32)
Bump lint job to latest Elixir/Erlang version (#31)
Release v1.2.3
Fix Elixir 1.14 warnings (#30)
Update ci.yml
Use `import Bitwise` instead of `use Bitwise` (#29)
Update plug link (#26)
Update crypto.ex
Rename arg for clarity in Plug.Crypto.encrypt/4 (#25)
Run formatter
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
1.3.0 (from changelog)
1.2.1 (from changelog)
1.2.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
Release v1.3.0 (#135)
Move docs to OTP 27 ex_doc support (#134)
Update README.md
Add latest Erlang 26.x to CI, bump rebar3, and GitHub actions (#131)
Ability to return extra measurements from :telemetry.span (#130)
Hide telemetry_test:handle_event/4 in the docs (#128)
Release 1.2.1 (#125)
replace local function capture in telemetry_test (#124)
Fix docs generation (#123)
Release 1.2.0 (#121)
Fix example in docs (#122)
Add telemetry_test (#118)
Update versions on CI (#120)
Update documentation on telemetry:span/3 (#117)
Point to new repo (#116)
Update documentation on telemetry:span/3 (#113)
Post 1.1.0 updates (#108)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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