chore(deps): update dependency oauth2 to v2
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| oauth2 (source) | major | ~> 0.9 -> ~> 2.0 |
Release Notes
scrogson/oauth2 (oauth2)
v2.1.0
Improvements
- Now you can have a lot more control over your http client, including selecting what client you are using from the adapters available for Tesla. You can also easily add logging and tracing with middleware.
Backward Incompatible Changes
-
No longer directly using hackney it's still possible to use it through a Tesla adapter. To keep all your tweaks working correctly you'll need to add these settings:
In mix.exs
mix.exs
defp deps do
Add the dependency
[
{:oauth2, "~> 2.0"},
{:hackney, "~> 1.18"} # This is the new line you need to add
]
end
```
In config:
elixir config :oauth2, adapter: Tesla.Adapter.Hackney
v2.0.1
Bug fixes
- Fix incorrect Accept header when requesting token
v2.0.0
Bug fixes (possibly backwards incompatible)
- Ensure that the OAuth client is authenticated via Authorization header as described in the spec (#131).
v1.0.1
Bug fixes
- Always use the provided serializer if one is registered (#132)
v1.0.0
Backward Incompatible Changes
- There is no longer a default serializer for
application/json. Please make sure to register a serializer withOAuth2.Client.put_serializer/3. - Serializers are now registered via
OAuth2.Client.put_serializer/3. This change allows applications wrappingoauth2a way to provide default serializers without requiring the user to manually configure a serializer.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!
-- conventional-commit-lint bot https://conventionalcommits.org/