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/ui-angular@6.0.0

Major Changes

• #7047 aa5e7192561a029307780ccf71823699021032da Thanks @bobbor! - Upgrade to Angular 20. The minimum supported Angular version is now 20.0.0; Angular 19 and below are no longer supported. The library is compiled with the Angular 20 compiler (partial-Ivy output is forward-compatible only).

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e]:
  • @aws-amplify/ui@6.15.5

@aws-amplify/ui-react-storage@3.18.0

Minor Changes

• #7046 25e8d96a4c8bee19409cf44f2df7856b52e56260 Thanks @bobbor! - feat(storage): folder download support in StorageBrowser

  Enable downloading folders (and mixed file/folder selections) from the
  StorageBrowser download action. Previously the download button was disabled
  whenever the selection contained a folder.

  Folders are expanded to their files at the view level before the download
  runs: the DownloadView lists folder contents on open (with a "listing
  folder contents" state), so the resolved files render as rows and the archive
  is only dispatched once every selected folder is fully enumerated. Each file
  preserves its folder-relative path inside the zip. A single-folder selection
  names the archive after that folder; other selections use the longest common
  ancestor directory of the downloaded files. Building on the service worker
  streaming download, the zip transfer itself uses constant memory; folder
  enumeration holds the file listing in memory and is capped at 5000 files per
  download, above which the download is blocked with a message instead of
  producing a truncated archive.

  Also: individual expanded files can be removed from the pending download,
  enumeration can be cancelled or retried, and empty/errored enumerations are
  surfaced without starting a partial download.

• #7044 51bb14dfdc4209938dd17480a967218585f8c8d4 Thanks @bobbor! - feat(storage): service worker streaming zip download

  Replace the in-memory blob-based zip download with a service worker streaming
  architecture for StorageBrowser multi-file downloads. Files are streamed
  sequentially into a zip archive delivered via a service worker, removing the
  memory ceiling of the previous blob approach. Falls back to blob collection
  when the service worker is unavailable (unsupported browser, missing file, or
  insecure context).

  Note: per-file progress is now reported download-only by design — it reflects
  bytes read from S3, not zip finalization. Because entries are stored without
  compression (level: 0), the write/finalization phase is near-instant, so
  progress transitions directly from downloading to complete without a separate
  "zipping"/finishing phase.

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e, 379f6c05bf36d0341de36441097ddb7984151e9c]:
  • @aws-amplify/ui@6.15.5
  • @aws-amplify/ui-react@6.15.5
  • @aws-amplify/ui-react-core@3.6.5

@aws-amplify/ui-react@6.15.5

Patch Changes

• #6962 379f6c05bf36d0341de36441097ddb7984151e9c Thanks @ashuvssut! - Fix Metro warnings by explicitly exporting dist CSS entrypoints in package.json. Added ./dist/styles.css export aliases to prevent Metro from implicitly falling back to file-based resolution.

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e]:

  • @aws-amplify/ui@6.15.5
  • @aws-amplify/ui-react-core@3.6.5

@aws-amplify/ui-react-core@3.6.5

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e]:
  • @aws-amplify/ui@6.15.5

@aws-amplify/ui-react-core-notifications@2.3.5

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e]:
  • @aws-amplify/ui@6.15.5
  • @aws-amplify/ui-react-core@3.6.5

@aws-amplify/ui-react-geo@2.3.5

Patch Changes

• Updated dependencies []:
  • @aws-amplify/ui-react-core@3.6.5

@aws-amplify/ui-react-liveness@3.6.8

Patch Changes

• #7069 daa76aec4ffe2c0ed8cd381c54e4e95feff8097c Thanks @pranavosu! - Widen @aws-sdk/client-rekognitionstreaming to ^3.974.0 and @aws-sdk/util-format-url to ^3.972.37. The previous exact pin on 3.967.0 transitively pinned @aws-sdk/core@3.967.0 -> @aws-sdk/xml-builder@3.965.0 -> fast-xml-parser@5.2.5, which consumers could not override without a forced resolution and which triggers scanner findings for CVE-2026-26278 and CVE-2026-25896. From 3.974.0 onward the SDK ranges its own @aws-sdk/core dependency, which resolves to a @aws-sdk/xml-builder that no longer depends on fast-xml-parser at all, and future SDK patches now flow through without another pin bump.

• #6962 379f6c05bf36d0341de36441097ddb7984151e9c Thanks @ashuvssut! - Fix Metro warnings by explicitly exporting dist CSS entrypoints in package.json. Added ./dist/styles.css export aliases to prevent Metro from implicitly falling back to file-based resolution.

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e, 379f6c05bf36d0341de36441097ddb7984151e9c]:

  • @aws-amplify/ui@6.15.5
  • @aws-amplify/ui-react@6.15.5

@aws-amplify/ui-react-native@2.7.5

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e]:
  • @aws-amplify/ui@6.15.5
  • @aws-amplify/ui-react-core@3.6.5
  • @aws-amplify/ui-react-core-notifications@2.3.5

@aws-amplify/ui-react-notifications@2.3.5

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e, 379f6c05bf36d0341de36441097ddb7984151e9c]:
  • @aws-amplify/ui@6.15.5
  • @aws-amplify/ui-react@6.15.5
  • @aws-amplify/ui-react-core@3.6.5
  • @aws-amplify/ui-react-core-notifications@2.3.5

@aws-amplify/ui-svelte@1.1.5

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e]:
  • @aws-amplify/ui@6.15.5

@aws-amplify/ui@6.15.5

Patch Changes

• #7055 21fa602576b12fa59c0101b52eff8551d778352e Thanks @ahmedhamouda78! - fix(ui): render locale-correct punctuation in Authenticator delivery messages (i18n)

  getDeliveryMessageText joined the translated delivery-message fragments with a
  hardcoded ASCII period, producing incorrect punctuation for locales whose
  sentence terminator differs — e.g. Japanese and Chinese (which use the
  ideographic full stop 。) and Thai (which uses none). The terminator is now
  derived from the script of the surrounding translated copy, so each locale
  renders its own punctuation.

  This is an internal change with no public API impact: no translation keys are
  added or changed, the translate() signature is unchanged, existing customer
  vocabulary overrides on the documented keys keep working, and English output is
  byte-identical. Fixes Wrong, hardcoded punctuation in Japanese #6966.

@aws-amplify/ui-vue@4.4.5

Patch Changes

• Updated dependencies [21fa602576b12fa59c0101b52eff8551d778352e]:
  • @aws-amplify/ui@6.15.5

@aws-amplify/ui-test-utils@0.1.5

Patch Changes

• Updated dependencies [25e8d96a4c8bee19409cf44f2df7856b52e56260, 51bb14dfdc4209938dd17480a967218585f8c8d4]:
  • @aws-amplify/ui-react-storage@3.18.0