Skip to content

Bump axios and aws-amplify - #10

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

Bump axios and aws-amplify#10
dependabot[bot] wants to merge 1 commit into
feature/nima/initial_deployment_attemptfrom
dependabot/npm_and_yarn/multi-0a30c75499

Conversation

@dependabot

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

Copy link
Copy Markdown

Bumps axios and aws-amplify. These dependencies needed to be updated together.
Updates axios from 0.21.1 to 1.19.0

Release notes

Sourced from axios's releases.

v1.19.0 - July 22, 2026

This release raises the form-data security floor, adds configuration and type-system capabilities, and fixes NO_PROXY matching, interceptor errors, progress reporting, and serialization edge cases.

🔒 Security Fixes

  • Multipart Form Data: Raised the form-data dependency floor to ^4.0.6, preventing fresh installations from resolving versions affected by the CRLF injection vulnerability GHSA-hmw2-7cc7-3qxx (GHSA-hmw2-7cc7-3qxx). (#11028)

🚀 New Features

  • Configuration Extensibility: Preserved own-enumerable symbol-keyed fields through mergeConfig and added a generic params type across public TypeScript declarations, responses, errors, adapters, and serializers. (#11043, #11081)
  • Header Parameter Parsing: Added the opt-in AxiosHeaders.parseParameters() parser for quote-aware, RFC-style HTTP parameter parsing while preserving legacy parsing behavior. (#11051)
  • HTTP Status Codes: Added the missing Cloudflare 520 WebServerReturnsAnUnknownError status and matching ESM/CJS declarations. (#11067)

🐛 Bug Fixes

  • Form Data Conversion: Limited formDataToJSON path splitting to dot and bracket notation, preserving literal punctuation in keys, and removed browser-facing Buffer.from usage from toFormData to avoid unnecessary polyfills. (#11006, #11018)
  • Proxy Bypass: Canonicalized IPv4 shorthand, octal, and hexadecimal forms during NO_PROXY matching and honored * entries within comma- or space-separated bypass lists. (#11029, #11053)
  • Cancellation: Propagated already-aborted input signals immediately when composing abort signals. (#11035)
  • Header Handling: Preserved empty first values for duplicate singleton headers and made AxiosHeaders#getSetCookie() consistently return arrays for present values. (#11036, #11037)
  • URL Handling: Included normalized, safely redacted offending URLs in malformed-protocol errors and removed repeated trailing slashes when combining base URLs. (#11024, #11038)
  • Progress Events: Clamped malformed negative progress values to zero and ensured final Node.js download progress events are delivered before streamed responses close. (#11039, #11040)
  • Error and JSON Serialization: Serialized Set values as arrays in JSON-compatible snapshots and synthesized useful AxiosError messages from otherwise-empty AggregateError instances. (#11044, #11059)
  • Content-Length Enforcement: Corrected base64 data: URL size estimation so maxContentLength is enforced consistently by the HTTP and Fetch adapters. (#11061)
  • Synchronous Interceptors: Prevented requests from being dispatched after synchronous request interceptors fail unless their paired rejection handler resolves successfully. (#11071)

🔧 Maintenance & Chores

  • Dependencies: Updated development and test tooling, the docs fixture's Axios version, and GitHub Actions integrations including Checkout, Setup Node, Setup Deno, and Zizmor. (#11031, #11055, #11056, #11058, #11079, #11080, #11088, #11089, #11090)
  • Build Outputs: Limited sourcemap generation to published minified bundles, removing broken map references from non-minified builds. (#11054)
  • Form Data Internals: Centralized FormData header handling and made the Node.js adapter tolerate getHeaders() returning undefined under the content-only policy. (#11062)
  • Developer Experience: Ignored common local AI-tooling directories and fixed a constant-reassignment crash when the development sandbox serves its root path. (#11032, #11073)
  • Documentation: Updated sponsor information, clarified that baseURL is not a path-security boundary, scoped provenance claims to attested releases, and corrected the configuration-defaults documentation. (#11041, #11068, #11076, #11078)
  • Publishing: Simplified v1 publishing to use the npm version bundled with Node.js 26 and updated package metadata for the 1.19.0 release. (#11083, #11095)

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve Axios:

... (truncated)

Changelog

Sourced from axios's changelog.

v1.19.0 — July 22, 2026

This release raises the form-data security floor, adds configuration and type-system capabilities, and fixes NO_PROXY matching, interceptor errors, progress reporting, and serialization edge cases.

🔒 Security Fixes

  • Multipart Form Data: Raised the form-data dependency floor to ^4.0.6, preventing fresh installations from resolving versions affected by the CRLF injection vulnerability GHSA-hmw2-7cc7-3qxx (GHSA-hmw2-7cc7-3qxx). (#11028)

🚀 New Features

  • Configuration Extensibility: Preserved own-enumerable symbol-keyed fields through mergeConfig and added a generic params type across public TypeScript declarations, responses, errors, adapters, and serializers. (#11043, #11081)
  • Header Parameter Parsing: Added the opt-in AxiosHeaders.parseParameters() parser for quote-aware, RFC-style HTTP parameter parsing while preserving legacy parsing behavior. (#11051)
  • HTTP Status Codes: Added the missing Cloudflare 520 WebServerReturnsAnUnknownError status and matching ESM/CJS declarations. (#11067)

🐛 Bug Fixes

  • Form Data Conversion: Limited formDataToJSON path splitting to dot and bracket notation, preserving literal punctuation in keys, and removed browser-facing Buffer.from usage from toFormData to avoid unnecessary polyfills. (#11006, #11018)

  • Proxy Bypass: Canonicalized IPv4 shorthand, octal, and hexadecimal forms during NO_PROXY matching and honored * entries within comma- or space-separated bypass lists. (#11029, #11053)

  • Cancellation: Propagated already-aborted input signals immediately when composing abort signals. (#11035)

  • Header Handling: Preserved empty first values for duplicate singleton headers and made AxiosHeaders#getSetCookie() consistently return arrays for present values. (#11036, #11037)

  • URL Handling: Included normalized, safely redacted offending URLs in malformed-protocol errors and removed repeated trailing slashes when combining base URLs. (#11008, #11038)

  • Progress Events: Clamped malformed negative progress values to zero and ensured final Node.js download progress events are delivered before streamed responses close. (#11039, #11040)

  • Error and JSON Serialization: Serialized Set values as arrays in JSON-compatible snapshots and synthesized useful AxiosError messages from otherwise-empty AggregateError instances. (#11044, #11059)

  • Content-Length Enforcement: Corrected base64 data: URL size estimation so maxContentLength is enforced consistently by the HTTP and Fetch adapters. (#11061)

  • Synchronous Interceptors: Prevented requests from being dispatched after synchronous request interceptors fail unless their paired rejection handler resolves successfully. (#11071)

🔧 Maintenance & Chores

  • Dependencies: Updated development and test tooling, the docs fixture's Axios version, and GitHub Actions integrations including Checkout, Setup Node, Setup Deno, and Zizmor. (#11031, #11055, #11056, #11058, #11079, #11080, #11088, #11089, #11090)
  • Build Outputs: Limited sourcemap generation to published minified bundles, removing broken map references from non-minified builds. (#11054)
  • Form Data Internals: Centralized FormData header handling and made the Node.js adapter tolerate getHeaders() returning undefined under the content-only policy. (#11062)
  • Developer Experience: Ignored common local AI-tooling directories and fixed a constant-reassignment crash when the development sandbox serves its root path. (#11032, #11073)
  • Documentation: Updated sponsor information, clarified that baseURL is not a path-security boundary, scoped provenance claims to attested releases, and corrected the configuration-defaults documentation. (#11041, #11068, #11076, #11078)
  • Publishing: Simplified v1 publishing to use the npm version bundled with Node.js 26 and updated package metadata for the 1.19.0 release. (#11083, #11095)

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve Axios:

... (truncated)

Commits
  • 311fcc5 chore(release): prepare release 1.19.0 (#11095)
  • cb4fd74 chore(deps): bump axios from 1.16.1 to 1.18.1 in /docs (#11088)
  • 004c93a chore(deps): bump actions/setup-node from 6.4.0 to 7.0.0 in the github-action...
  • 122edde chore(deps-dev): bump the development_dependencies group with 3 updates (#11089)
  • c44f8d0 ci: use bundled npm for v1 publish (#11083)
  • 878bb29 fix(sandbox): resolve TypeError on constant variable path assignment (#11073)
  • a092bae fix(core): synchronous interceptors swallow errors and proceed with request (...
  • 3041b8f feat(HttpStatusCode): add missing 520 status code (#11067)
  • 58b16c8 refactor(helpers): extract duplicated setFormDataHeaders into a shared helper...
  • 3077e62 feat(types): Allow the Params property to be typed, instead of any (#11081)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for axios since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Updates aws-amplify from 3.3.14 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

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

aws-amplify@6.18.0

Minor Changes

Patch Changes

... (truncated)

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

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
  • 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...
  • d648403 Version Packages (main) (#14873)
  • 49d9e82 feat(analytics): warn on deprecated default Pinpoint exports (#14877)
  • aaeb630 feat(core): add ServiceWorker onStateChange telemetry hook (#14867)
  • eed1462 feat(analytics): add configureAutoTrack support for Kinesis and Kinesis Fireh...
  • 7d85285 Version Packages (main) (#14810)
  • 6f5a076 fix(aws-amplify): sync Cognito auth config on reconfigure (#14819)
  • 37aa603 chore: Update registry.directory and homepage for package.json (#14794)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by aws-amplify-ops, a new releaser for aws-amplify since your current version.


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.

@dependabot
Bump axios and aws-amplify
97d3630 
Bumps [axios](https://github.com/axios/axios) and [aws-amplify](https://github.com/aws-amplify/amplify-js/tree/HEAD/packages/aws-amplify). These dependencies needed to be updated together.

Updates `axios` from 0.21.1 to 1.19.0
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v0.21.1...v1.19.0)

Updates `aws-amplify` from 3.3.14 to 6.20.0
- [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@6.20.0/packages/aws-amplify)

---
updated-dependencies:
- dependency-name: axios
  dependency-version: 1.19.0
  dependency-type: direct:production
- dependency-name: aws-amplify
  dependency-version: 6.20.0
  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 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants