Repository navigation
chore(deps): update dependency social-auth-core to v6.1.0 - #554
Merged
Merged
Conversation
Documentation build overview
13 files changed ·
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
==6.0.0→==6.1.0Release Notes
python-social-auth/social-core (social-auth-core)
v6.1.0Compare Source
Removed
docker) because its authorization,token, and profile endpoints are no longer available. Remove
social_core.backends.docker.DockerOAuth2from backend configuration.See #1176.
live),Evernote Sandbox (
evernote-sandbox), PixelPin (pixelpin-openidconnect),Behance (
behance), and NGP VAN ActionID OpenID (actionid-openid). Theirauthentication endpoints have been retired or are no longer available; see
#1176.
Remove
social_core.backends.live.LiveOAuth2,social_core.backends.evernote.EvernoteSandboxOAuth,social_core.backends.pixelpin.PixelPinOpenIDConnect,social_core.backends.behance.BehanceOAuth2, andsocial_core.backends.ngpvan.ActionIDOpenIDfrom backend configuration.Live Connect users can configure
social_core.backends.microsoft.MicrosoftOAuth2(
microsoft-graph), but identifiers are not compatible and existing accountassociations are not migrated automatically. Production Evernote remains
supported. This removes the old ActionID OpenID integration, not the ActionID
service. Existing stored account associations are not deleted.
Security
pickle. In-progress OpenID logins with old session state must restart; existing
linked accounts, provider associations, and authenticated sessions are unchanged.
Fixed
(provider, id_key, uid)lookups instead of scanning stored JSON during authentication. Configure
backend-scoped
LEGACY_ID_KEYSfor explicit identifier changes.for audited built-in transitions that lacked evidence in social-core 5.2.0.
Conflicting evidence always stops authentication, including when
ALLOW_UNVERIFIED_LEGACY_UID_MIGRATIONis explicitly enabled. Missing evidencestops authentication unless the transition's compatibility policy allows it.
Nonefor unavailable names instead of invented emptystrings, preventing logins and account associations from clearing existing
names. Name normalization still fills missing or blank fields from available
names, but preserves unavailable components when derivation produces nothing.
Explicit provider-supplied empty strings remain valid profile updates.
defaults apply instead of inserting null values into non-null columns,
including when only name fields are configured.
alias is blank, while preserving blanks when no usable name is supplied.
runs with optimization enabled.
invalidate()andrefresh()controls.Breaking
evidence_keyargument to
migrate_social_auth()and revalidate supplied evidence atomically.The pipeline now passes keyed
legacy_identifiers;legacy_uidsandget_legacy_user_ids()remain available for compatibility.Changed
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.