Skip to content

Update guardian 2.2.1 → 2.3.2 (minor) #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Sep 13, 2023

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?

✳️ guardian (2.2.1 → 2.3.2) · Repo · Changelog

Release Notes

2.3.2

What's Changed

  • fix: publishing the changelog to hexdocs by @yordis in #716
  • chore: bump elixir version by @yordis in #724
  • fix: generating timestamp using os_time instead of system_time by @yordis in #725

Full Changelog: v2.3.1...v2.3.2

2.3.1

What's Changed

  • Use erlef/setup-beam and prettify yaml file by @kianmeng in #705
  • doc: Clarify session storage behavior on sign_in in README by @KaylaBrady in #714
  • Users should be able to change most config values at runtime by @geofflane in #715

New Contributors

Full Changelog: v2.3.0...v2.3.1

2.3.0

What's Changed

New Contributors

Full Changelog: v2.2.4...v2.3.0

2.2.4

What's Changed

New Contributors

Full Changelog: v2.2.3...v2.2.4

2.2.3

What's Changed

  • Ensure that badly-formatted tokens don't raise an exception by @giddie in #697

Full Changelog: v2.2.2...v2.2.3

2.2.2

What's Changed

New Contributors

Full Changelog: v2.2.1...v2.2.2

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

Commits

See the full diff on Github. The new version differs by 19 commits:

↗️ jose (indirect, 1.11.2 → 1.11.6) · Repo · Changelog

Release Notes

1.11.6

1.11.6 (2023-07-18)

  • Fixes
    • Use sha256 instead of sha when validating RSA signing supportability, thanks to @pavledjo; see #142.

1.11.5

  • Fixes
    • Remove dependency on parse_transform for jose_base64 and jose_base64url.

1.11.4

  • Enhancements
    • Add support for native crypto operations for Ed25519 and Ed448, thanks to @brettbeatty; see #123.
    • Add support for native crypto operations for ChaCha20-Poly1305 and XChaCha20-Poly1305, when available.
    • Add support for libsodium operations for XChaCha20-Poly1305, when available.
    • Add support for thoas JSON encode/decode, thanks to @michaelklishin; see #126.
    • Add support for ES256K which uses the secp256k1 curve and RS1 signatures (see 291dbb8).
    • Add support for ECDH-1PU JOSE.JWK.box_encrypt_ecdh_1pu and ECDH-ES JOSE.JWK.box_encrypt_ecdh_es and document the deprecated JOSE.JWK.box_encrypt.
    • Add support for ECDH-SS JOSE.JWK.box_encrypt_ecdh_ss.
    • Hide kty field when inspecting %JOSE.JWK{} strict, thanks to @spencerdcarlson; see #139
  • Fixes
    • Version mismatch causing rebar3 to constantly try to update; see #122.
    • Fix Ed25519 and Ed448 key DER/PEM encode/decode for OTP 25.
    • Fix Ed25519ctx, Ed25519ph, Ed448, and Ed448ph when dealing with contexts so the implementation matches IETF RFC 8032.
    • Drop direct usage of crypto:hmac/4, thanks to @thalesmg; see #136
    • Replace incorrect usage of -include_lib with -include, thanks to @Richiban; see #140
    • Update the CI jobs so they actually run the Elixir tests, thanks to @moogle19; see #137
    • Change the master branch to main.

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

Commits

See the full diff on Github. The new version differs by 41 commits:

↗️ mime (indirect, 2.0.3 → 2.0.5) · Repo · Changelog

Release Notes

2.0.5 (from changelog)

  • Allow conflicting extension to be overridden

2.0.4 (from changelog)

  • Only returns extensions from known suffixes
  • Allow mime types to be fully overridden

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

Commits

See the full diff on Github. The new version differs by 8 commits:

↗️ plug (indirect, 1.13.6 → 1.14.2) · Repo · Changelog

Release Notes

1.14.2 (from changelog)

Bug fixes

  • Properly deprecate Plug.Adapters.Cowboy before removal

1.14.1 (from changelog)

Enhancements

  • Add nest_all_json option to JSON parser
  • Make action on Plug.Debugger page look like a button
  • Better formatting of exceptions on the error page
  • Provide stronger response header validation

1.14.0 (from changelog)

Require Elixir v1.10+.

Enhancements

  • Add Plug.Conn.prepend_req_headers/2 and Plug.Conn.merge_req_headers/2
  • Support adapter upgrades with Plug.Conn.upgrade_adapter/3
  • Add "Copy to Markdown" button in exception page
  • Support exclusive use of tlsv1.3

Bug fixes

  • Make sure last parameter works within maps

Deprecations

  • Deprecate server pushes as they are no longer supported by browsers

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.

↗️ plug_crypto (indirect, 1.2.2 → 1.2.5) · Repo · Changelog

Release Notes

1.2.5 (from changelog)

  • Allow AAD to be given as iolist

1.2.4 (from changelog)

  • Allow AAD to be given as argument on message encryptor

1.2.3 (from changelog)

  • Remove warnings on Elixir v1.14

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

Commits

See the full diff on Github. The new version differs by 17 commits:

↗️ telemetry (indirect, 1.1.0 → 1.2.1) · Repo · Changelog

Release Notes

1.2.1 (from changelog)

Fixed

  • Fixed a local handler warning log when using telemetry_test. (#124)

1.2.0 (from changelog)

Added

  • Added telemetry_test module for testing telemetry events. (#118)

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

Commits

See the full diff on Github. The new version differs by 11 commits:


👉 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 Status

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 cancel merge
Cancels automatic merging of this PR
@​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)

@depfu depfu bot added the depfu label Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants