chore(deps): bump amplify_core from 1.0.0-next.8+1 to 1.2.0 in /infra

[dependabot]

Bumps amplify_core from 1.0.0-next.8+1 to 1.2.0.

Release notes

Sourced from amplify_core's releases.

1.2.0

Fixes

• fix(api): GraphQL subscription with custom domain formats URI correctly (#3148)
• fix(auth): Attribute key equality (#3136)
• fix(auth): signOut after user deletion (#3162)
• fix(core): Disallowed JS tearoff (#3150)
• fix(storage): API doc errors

Features

• feat(storage): using path style URLs when bucket name contains dots

1.1.0

Features

• Dart 3 support (must update Dart SDK constraint to ^3.0.0)
• feat(core): add granular model read operations (aws-amplify/amplify-flutter#2611)

Fixes

• fix(notifications): configure call hangs on Flutter app hot restart (aws-amplify/amplify-flutter#3013)
• fix(repo): AGP 8.0 compatibility (aws-amplify/amplify-flutter#2942)

v1.0.0

We are thrilled to release version 1.0 of the Amplify Flutter libraries!

This release introduces a full rewrite of the Amplify libraries in Dart, allowing you to build AWS cloud-connected applications on every platform Flutter supports (iOS, Android, Web, macOS, Windows, and Linux).

If you've been using v0 in production, you can now safely migrate to v1. Check out our migration guide for more information.

New Features

Analytics Category

• You can now save to the UserAttributes field of a Pinpoint Endpoint by passing an AWSPinpointUserProfile to Amplify.Analytics.identifyUser.
• The autoFlushEventsInterval in Analytics config can now be set in seconds to control how often cached events are auto-flushed. Beforehand, this value was inconsistently read as seconds on iOS and milliseconds on Android.

API Category

• GraphQLRequest now has an authorizationMode property so callers can specify the authorization mode directly.
• GraphQLRequest now has a headers property to specify HTTP headers.
• GraphQL subscriptions will automatically reconnect when losing internet, or when changing from Wi-fi to cellular data or vice versa.
• GraphQL model helpers now support custom primary keys.
• GraphQL subscription model helpers (ModelSubscriptions) now support a where clause to use server-side subscription filters via model helpers.

Auth Category

• fetchAuthSession now supports a forceRefresh parameter which, when passed, will refresh User Pool tokens and AWS credentials regardless if they’ve expired.
• The result of Amplify.Auth.signUp now provides the user ID of the created user. Previously this was only available after signing in.
• Custom OAuth providers are now configurable when signing in via Hosted UI.
• A new federateToIdentityPool API has been added to the Cognito plugin which allows federating directly into an Identity Pool to receive AWS credentials using a third-party identity provider (IdP) token.
  • Note: Since this method is only available on the Cognito plugin, it must be called directly on the plugin. The Cognito plugin can be retrieved by calling Amplify.Auth.getPlugin(AmplifyAuthCognito.pluginKey) anytime after configuration.
  • This method prevents usage of any User Pool-related methods. It should only be used in scenarios where you need AWS credentials and already have a mechanism for retrieving OIDC tokens from a third-party IdP.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #418.