Skip to content

Bump js-cookie and aws-amplify in /2023-01-31-LocalStack-Community-Meetup/demo-3/client-application-react - #34

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/2023-01-31-LocalStack-Community-Meetup/demo-3/client-application-react/multi-eee193a7b5
Open

Bump js-cookie and aws-amplify in /2023-01-31-LocalStack-Community-Meetup/demo-3/client-application-react#34
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/2023-01-31-LocalStack-Community-Meetup/demo-3/client-application-react/multi-eee193a7b5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 27, 2026

Copy link
Copy Markdown

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

Updates js-cookie from 2.2.1 to 3.0.8

Release notes

Sourced from js-cookie's releases.

v3.0.8

  • Restore ES5 compatibility, inadvertently broken in 3.0.7 - #959
  • Lift Node version restriction, inadvertently restricted to >= 20 in 3.0.7 - #956

v3.0.7

  • Prevent cookie attribute injection: CVE-2026-46625 (eb3c40e)
  • Add Partitioned attribute to readme (b994768)
  • Publish to npm registry via trusted publisher exclusively (4dc71be)
  • Ensure consistent behaviour for get('name') + get() (1953d30)

v3.0.5

  • Remove npm version restriction in package.json - #818

v3.0.4

  • Publish to npmjs.com with package provenance

v3.0.1

  • Make package.json accessible in export - #727

v3.0.0

  • Removed defaults in favor of a builder: now to supply an api instance with particular predefined (cookie) attributes there's Cookies.withAttributes(), e.g.:
const api = Cookies.withAttributes({
  path: '/',
  secure: true
})
api.set('key', 'value') // writes cookie with path: '/' and secure: true...
  • The attributes that an api instance is configured with are exposed as attributes property; it's an immutable object and unlike defaults cannot be changed to configure the api.
  • The mechanism to fall back to the standard, internal converter by returning a falsy value in a custom read converter has been removed. Instead the default converters are now exposed as Cookies.converter, which allows for implementing self-contained custom converters providing the same behavior:
const customReadConverter = (value, name) => {
  if (name === 'special') {
    return unescape(value)
  }
  return Cookies.converter.read(value)
}
  • withConverter() no longer accepts a function as argument to be turned into a read converter. It is now required to always pass an object with the explicit type(s) of converter(s):
const api = Cookies.withConverter({
  read: (value, name) => unescape(value)
})
  • The converter(s) that an api instance is configured with are exposed as converter property; it's an immutable object and cannot be changed to configure the api.
  • Started providing library as ES module, in addition to UMD module. The module field in package.json points to an ES module variant of the library.
  • Started using browser field instead of main in package.json (for the UMD variant of the library).
  • Dropped support for IE < 10.
  • Removed built-in JSON support, i.e. getJSON() and automatic stringifying in set(): use Cookies.set('foo', JSON.stringify({ ... })) and JSON.parse(Cookies.get('foo')) instead.
  • Removed support for Bower.

... (truncated)

Commits
  • d7a1096 Craft v3.0.8 release
  • 248e685 Use existing Chrome with puppeteer
  • fc04269 Remove QUnit related workaround in Grunt config
  • 265a685 Tidy up package lock file
  • 478e591 Disable Node deprecation DEP0044 for release workflow
  • 331d524 Fix node version config for E2E test job
  • 11d773d Ensure ECMAScript compatibility
  • d788646 Remove engines property from package
  • e7d9a4d Fix typo in test assertion message
  • b5fca24 Make credentials use explicit in release workflow
  • Additional commits viewable in compare view
Maintainer changes

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


Updates aws-amplify from 4.3.2 to 6.19.0

Release notes

Sourced from aws-amplify's releases.

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

aws-amplify@6.17.0

Minor Changes

Patch Changes

aws-amplify@6.16.4

Patch Changes

... (truncated)

Changelog

Sourced from aws-amplify's changelog.

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

6.17.0

Minor Changes

Patch Changes

... (truncated)

Commits
  • 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)
  • 3c7a96f Version Packages (main) (#14785)
  • 09d46a5 chore(release): Version packages
  • a59a10a Merge branch 'main' into feat/pre-signed-upload-url
  • 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 js-cookie and aws-amplify
259793f 
Bumps [js-cookie](https://github.com/js-cookie/js-cookie) to 3.0.8 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 `js-cookie` from 2.2.1 to 3.0.8
- [Release notes](https://github.com/js-cookie/js-cookie/releases)
- [Commits](js-cookie/js-cookie@v2.2.1...v3.0.8)

Updates `aws-amplify` from 4.3.2 to 6.19.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.19.0/packages/aws-amplify)

---
updated-dependencies:
- dependency-name: js-cookie
  dependency-version: 3.0.8
  dependency-type: indirect
- dependency-name: aws-amplify
  dependency-version: 6.19.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 Jul 27, 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