build(deps): bump aws-amplify from 6.19.0 to 6.20.0

[dependabot]

Bumps aws-amplify from 6.19.0 to 6.20.0.

Release notes

Sourced from aws-amplify's releases.

aws-amplify@6.20.0

Minor Changes

• #14866 bcdc02b Thanks @​soberm! - feat(notifications): add Amazon Connect Customer Profiles push notifications provider

  Push Notifications can now be delivered through Amazon Connect Customer Profiles via the new aws-amplify/push-notifications/customer-profiles sub-path export. The provider ships identifyUser, initializePushNotifications, registerDevice, and removeDevice alongside the transport-agnostic badge, permission, launch-notification, and notification/token listener APIs, with SigV4-signed device registration and client-side user-profile validation. Amplify.configure accepts the corresponding amazon_connect notifications configuration from amplify_outputs.json.

  Device registration follows the signed-in principal: initializePushNotifications registers the device when a push token is received and re-registers it on sign-in so an existing registration is re-homed to the authenticated principal. Because de-registration is authorized against the calling principal, applications should await removeDevice() before signOut() to stop delivery to a device.

  The default aws-amplify/push-notifications entry point emits a one-time ConsoleLogger notice at runtime directing customers to the Customer Profiles sub-path, since that entry point is backed by Amazon Pinpoint and AWS ends support for Amazon Pinpoint on October 30, 2026. Both changes are backwards compatible: existing exports keep their names, types, and signatures.

Patch Changes

• Updated dependencies [bcdc02b]:
  • @​aws-amplify/core@​6.18.0
  • @​aws-amplify/notifications@​2.1.0
  • @​aws-amplify/api@​6.3.29
  • @​aws-amplify/datastore@​5.1.10

Changelog

Sourced from aws-amplify's changelog.

6.20.0

Minor Changes

• #14866 bcdc02b Thanks @​soberm! - feat(notifications): add Amazon Connect Customer Profiles push notifications provider

  Push Notifications can now be delivered through Amazon Connect Customer Profiles via the new aws-amplify/push-notifications/customer-profiles sub-path export. The provider ships identifyUser, initializePushNotifications, registerDevice, and removeDevice alongside the transport-agnostic badge, permission, launch-notification, and notification/token listener APIs, with SigV4-signed device registration and client-side user-profile validation. Amplify.configure accepts the corresponding amazon_connect notifications configuration from amplify_outputs.json.

  Device registration follows the signed-in principal: initializePushNotifications registers the device when a push token is received and re-registers it on sign-in so an existing registration is re-homed to the authenticated principal. Because de-registration is authorized against the calling principal, applications should await removeDevice() before signOut() to stop delivery to a device.

  The default aws-amplify/push-notifications entry point emits a one-time ConsoleLogger notice at runtime directing customers to the Customer Profiles sub-path, since that entry point is backed by Amazon Pinpoint and AWS ends support for Amazon Pinpoint on October 30, 2026. Both changes are backwards compatible: existing exports keep their names, types, and signatures.

Patch Changes

• Updated dependencies [bcdc02b]:
  • @​aws-amplify/core@​6.18.0
  • @​aws-amplify/notifications@​2.1.0
  • @​aws-amplify/api@​6.3.29
  • @​aws-amplify/datastore@​5.1.10

Commits

• 5d8009f Version Packages (main) (#14898)
• e1067a9 fix(push-notifications): add customer-profiles subpath package.json for legac...
• bcdc02b feat(notifications): add Amazon Connect Customer Profiles provider for Push N...
• See full diff in compare view

[mergify]

Automatically approving dependabot

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request