Version Packages (main) - #635
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
March 31, 2026 15:01
19f1bb8 to
decb02f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
April 8, 2026 03:01
7145edc to
34d3144
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
April 13, 2026 09:01
74e094c to
4e2157a
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
April 21, 2026 15:01
4e2157a to
b3c0762
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
May 4, 2026 09:01
672aaf7 to
7d81271
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
May 12, 2026 21:01
88fd1bf to
d0c2f45
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
May 28, 2026 21:01
a056d6c to
238287b
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 4, 2026 15:01
238287b to
95de2b9
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
July 16, 2026 15:01
8c71c5f to
2dbcd4d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 20, 2026 15:01
2dbcd4d to
1b43907
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 30, 2026 09:01
1b43907 to
50d3462
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 4, 2026 15:01
be476c2 to
70de371
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 4, 2026 21:01
70de371 to
2ed59b2
Compare
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@aws-amplify/auth@6.20.1
Patch Changes
#14902
4661401Thanks @soberm! - fix(auth): allow prompt=none silent SSO to resume federated sessionssignInWithRedirectalways appendedidentity_provider=COGNITOto the/oauth2/authorizerequest when noprovideroridpIdentifierwas supplied. Cognito treatsidentity_provideras a provider selector, so pinning it toCOGNITOwhile requesting a silent sign in withoptions.prompt: 'NONE'restricted the attempt to native Cognito sessions. Users whose live hosted UI session originated from a federated IdP (for example Google or a SAML provider) were rejected witherror=login_requiredinstead of having their session resumed.identity_provideris now omitted only whenpromptis'NONE'and neitherprovidernoridpIdentifieris specified, which lets Cognito resume whichever session is already active. All other behavior is unchanged: an explicitproviderstill sendsidentity_provider, anidpIdentifierstill sendsidp_identifier, and the interactive no-argument call still defaults toidentity_provider=COGNITO.Fixes signInWithRedirect always sends identity_provider=COGNITO, preventing Cognito from resuming a federated session aws-amplify/amplify-js#14897
aws-amplify@6.20.1
Patch Changes
4661401]:@aws-amplify/pubsub@6.1.71
Patch Changes
4661401]: