Skip to content

Bump crypto-js and aws-amplify - #14

Open
dependabot[bot] wants to merge 1 commit into
feature/nima/initial_deployment_attemptfrom
dependabot/npm_and_yarn/multi-bd1cdaf211
Open

Bump crypto-js and aws-amplify#14
dependabot[bot] wants to merge 1 commit into
feature/nima/initial_deployment_attemptfrom
dependabot/npm_and_yarn/multi-bd1cdaf211

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 9, 2026

Copy link
Copy Markdown

Bumps crypto-js to 4.2.0 and updates ancestor dependency aws-amplify. These dependencies need to be updated together.

Updates crypto-js from 3.3.0 to 4.2.0

Commits

Updates aws-amplify from 3.3.14 to 3.4.3

Changelog

Sourced from aws-amplify's changelog.

Change Log

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

6.19.0

Minor Changes

  • #14854 eed1462 Thanks @​soberm! - feat(analytics): add configureAutoTrack support for Kinesis and Kinesis Firehose providers

  • #14867 aaeb630 Thanks @​soberm! - feat(core): add optional onStateChange telemetry hook to ServiceWorker.register(); deprecate implicit Pinpoint auto-recording of SW lifecycle events (opt-in, backwards compatible)

Patch Changes

  • #14877 49d9e82 Thanks @​soberm! - feat(analytics): warn on deprecated default (Pinpoint) exports

    The default (Amazon Pinpoint) Analytics APIs (record, identifyUser, configureAutoTrack, flushEvents) now emit a one-time ConsoleLogger deprecation warning at runtime, pointing customers to the supported sub-path exports (aws-amplify/analytics/kinesis, aws-amplify/analytics/kinesis-firehose, aws-amplify/analytics/personalize). AWS ends support for Amazon Pinpoint on October 30, 2026. This is non-breaking: types and signatures are preserved.

  • Updated dependencies [eed1462, 49d9e82, 9a3041c, aaeb630]:

    • @​aws-amplify/analytics@​7.1.0
    • @​aws-amplify/datastore@​5.1.9
    • @​aws-amplify/core@​6.17.0
    • @​aws-amplify/api@​6.3.28

6.18.0

Minor Changes

Patch Changes

... (truncated)

Commits
  • 1d3c5ee chore(release): Publish [ci skip]
  • 47c8c7c chore(release): releasing 3.4.2
  • d4f6dc0 chore(release): Publish [ci skip]
  • dedd564 feat(@​aws-amplify/datastore): DataStore - Multi-Auth (#8008)
  • ca75c47 chore(release): Publish [ci skip]
  • 30a8fa7 chore(release): Publish [ci skip]
  • 53ea147 chore(release): Publish [ci skip]
  • 030e3c9 chore(release): Publish [ci skip]
  • f8eafce chore(release): Publish [ci skip]
  • 92286f4 chore(release): Publish [ci skip]
  • Additional commits viewable 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [crypto-js](https://github.com/brix/crypto-js) to 4.2.0 and updates ancestor dependency [aws-amplify](https://github.com/aws-amplify/amplify-js/tree/HEAD/packages/aws-amplify). These dependencies need to be updated together.


Updates `crypto-js` from 3.3.0 to 4.2.0
- [Commits](brix/crypto-js@3.3.0...4.2.0)

Updates `aws-amplify` from 3.3.14 to 3.4.3
- [Release notes](https://github.com/aws-amplify/amplify-js/releases)
- [Changelog](https://github.com/aws-amplify/amplify-js/blob/main/packages/aws-amplify/CHANGELOG.md)
- [Commits](https://github.com/aws-amplify/amplify-js/commits/aws-amplify@3.4.3/packages/aws-amplify)

---
updated-dependencies:
- dependency-name: crypto-js
  dependency-version: 4.2.0
  dependency-type: indirect
- dependency-name: aws-amplify
  dependency-version: 3.4.3
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants