Version Packages (main)

[github-actions]

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@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

@aws-amplify/core@6.18.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.

@aws-amplify/notifications@2.1.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.

@aws-amplify/api@6.3.29

Patch Changes

• Updated dependencies []:
  • @aws-amplify/api-graphql@4.8.10

@aws-amplify/api-graphql@4.8.10

Patch Changes

• Updated dependencies [bcdc02b]:
  • @aws-amplify/core@6.18.0

@aws-amplify/datastore@5.1.10

Patch Changes

• Updated dependencies []:
  • @aws-amplify/api@6.3.29
  • @aws-amplify/api-graphql@4.8.10