Skip to content

Update django-allauth to 0.39.1#63

Closed
pyup-bot wants to merge 1 commit into
masterfrom
pyup/update-django-allauth-0.38.0-to-0.39.1
Closed

Update django-allauth to 0.39.1#63
pyup-bot wants to merge 1 commit into
masterfrom
pyup/update-django-allauth-0.38.0-to-0.39.1

Conversation

@pyup-bot

Copy link
Copy Markdown
Collaborator

This PR updates django-allauth from 0.38.0 to 0.39.1.

Changelog

0.39.1

*******************

Note worthy changes
-------------------

- The ``linkedin_oauth2`` provider now gracefully deals with old V1
data that might still be present in ``SocialAccount.extra_data``.

0.39.0

*******************

Note worthy changes
-------------------

- New providers: JupyterHub (OAuth2), Steam (OpenID)

- Refactor translations: Portuguese (Portugal).

- Add testing for Django 2.2 (no code changes required)

Backwards incompatible changes
------------------------------

- ``linkedin_oauth2``: As the LinkedIn V1 API is deprecated, the user info
endpoint has been moved over to use the API V2. The format of the user
``extra_data`` is different and the profile picture is absent by default.
Links

@pyup-bot

Copy link
Copy Markdown
Collaborator Author

Closing this in favor of #160

@pyup-bot pyup-bot closed this Aug 29, 2019
@vCra vCra deleted the pyup/update-django-allauth-0.38.0-to-0.39.1 branch August 29, 2019 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant