Skip to content

Bump the frontend-minor-patch group across 1 directory with 14 updates - #41

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/frontend-minor-patch-f50e9da337
Closed

Bump the frontend-minor-patch group across 1 directory with 14 updates#41
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/frontend-minor-patch-f50e9da337

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 29, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the frontend-minor-patch group with 14 updates in the /frontend directory:

Package From To
aws-amplify 6.20.0 6.22.0
lucide-react 1.44.0 1.48.0
mediasoup-client 3.23.1 3.24.1
react-router-dom 7.18.3 7.18.4
socket.io-client 4.8.3 4.8.4
tailwind-merge 3.6.0 3.7.0
web-vitals 6.2.1 6.2.2
@aws-amplify/backend 1.24.1 1.25.1
@aws-amplify/backend-cli 1.9.1 1.10.0
aws-cdk-lib 2.268.0 2.271.0
eslint-plugin-react-refresh 0.5.6 0.5.7
tsx 4.23.13 4.23.15
typescript-eslint 8.70.0 8.70.1
vite 8.2.2 8.3.1

Updates aws-amplify from 6.20.0 to 6.22.0

Release notes

Sourced from aws-amplify's releases.

aws-amplify@6.22.0

Minor Changes

  • #14954 a5e8df2 Thanks @​soberm! - feat(events): resolve subscription readiness via channel.subscribe().ready and add subscription id to the SUBSCRIPTION_ACK Hub event

Patch Changes

  • #14948 d8f5356 Thanks @​bobbor! - fix(auth): support user-pool sign-in through a local createAmplifyContext() without Amplify.configure()

    Makes a locally created AmplifyContext (createAmplifyContext(), without calling Amplify.configure()) usable end-to-end for Cognito user-pool auth:

    • Amplify.getConfig() again returns an empty config ({}) with a warning before configure() instead of throwing NoAmplifyContextError, restoring the released 6.20.0 contract that the explicit-AmplifyContext migration (#14931) unintentionally changed.
    • Cognito sign-in, fetchAuthSession, and the device APIs now resolve the per-context token orchestrator at the flow entry point (falling back to the global singleton for the Amplify.configure() path), so tokens persist to and are read from the same per-context store. The global Amplify.configure() path is unchanged.
    • Known limitation: OAuth (signInWithRedirect) sign-in tokens still cache to the global orchestrator, because OAuth completion runs after a full-page redirect via enableOAuthListener, at which point no AmplifyContext survives — so a local createAmplifyContext() that initiates signInWithRedirect cannot read its OAuth tokens back per-context. This fix covers user-pool (non-redirect) sign-in.

  • Updated dependencies [d8f5356]:

    • @​aws-amplify/auth@​6.21.1
    • @​aws-amplify/core@​6.19.1
    • @​aws-amplify/api@​6.4.1
    • @​aws-amplify/datastore@​5.1.12
Changelog

Sourced from aws-amplify's changelog.

6.22.0

Minor Changes

  • #14954 a5e8df2 Thanks @​soberm! - feat(events): resolve subscription readiness via channel.subscribe().ready and add subscription id to the SUBSCRIPTION_ACK Hub event

Patch Changes

  • #14948 d8f5356 Thanks @​bobbor! - fix(auth): support user-pool sign-in through a local createAmplifyContext() without Amplify.configure()

    Makes a locally created AmplifyContext (createAmplifyContext(), without calling Amplify.configure()) usable end-to-end for Cognito user-pool auth:

    • Amplify.getConfig() again returns an empty config ({}) with a warning before configure() instead of throwing NoAmplifyContextError, restoring the released 6.20.0 contract that the explicit-AmplifyContext migration (#14931) unintentionally changed.
    • Cognito sign-in, fetchAuthSession, and the device APIs now resolve the per-context token orchestrator at the flow entry point (falling back to the global singleton for the Amplify.configure() path), so tokens persist to and are read from the same per-context store. The global Amplify.configure() path is unchanged.
    • Known limitation: OAuth (signInWithRedirect) sign-in tokens still cache to the global orchestrator, because OAuth completion runs after a full-page redirect via enableOAuthListener, at which point no AmplifyContext survives — so a local createAmplifyContext() that initiates signInWithRedirect cannot read its OAuth tokens back per-context. This fix covers user-pool (non-redirect) sign-in.

  • Updated dependencies [d8f5356]:

    • @​aws-amplify/auth@​6.21.1
    • @​aws-amplify/core@​6.19.1
    • @​aws-amplify/api@​6.4.1
    • @​aws-amplify/datastore@​5.1.12

6.21.0

Minor Changes

  • #14931 736d81d Thanks @​bobbor! - feat: explicit AmplifyContext support across all categories.

    Adds context-first overloads (fn(ctx, input)) to category APIs alongside the existing singleton-based forms, a public createAmplifyContext(resourcesConfig, libraryOptions?) factory for isolated per-request/per-tenant contexts, per-request context isolation in @aws-amplify/adapter-nextjs SSR, typed misuse errors (InvalidAmplifyContextError, NoAmplifyContextError), and a shared testing entry (@aws-amplify/core/internals/testing).

    Backward compatible: existing application code — including pre-context SSR operation: (contextSpec) => fetchAuthSession(contextSpec) — compiles and behaves unchanged via deprecated type aliases. Includes two api-graphql bug fixes: SSR request clients now honor client-level options (previously silently dropped), and events error messages accurately describe failures.

    Compatibility surface and version guidance:

    • Resources config is now deep-frozen after Amplify.configure() and createAmplifyContext() (previously frozen only at the top level). Code that mutated a nested config field post-configure — always unsupported — now throws in strict mode instead of silently succeeding.
    • Deprecated AmplifyServer type aliases (Context, ContextSpec, ContextToken, RunOperationWithContext) and functional createAmplifyServerContext / getAmplifyServerContext / destroyAmplifyServerContext shims are restored on the internals/adapter-core entries so previously published @aws-amplify/adapter-nextjs versions keep working. They will be removed in the next major.
    • Peer minimums are raised (@aws-amplify/core to ^6.19.0 across category packages;

... (truncated)

Commits

Updates lucide-react from 1.44.0 to 1.48.0

Release notes

Sourced from lucide-react's releases.

Version 1.48.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.47.0...1.48.0

Version 1.47.0

What's Changed

New Contributors

... (truncated)

Commits

Updates mediasoup-client from 3.23.1 to 3.24.1

Release notes

Sourced from mediasoup-client's releases.

3.24.1

Full Changelog: versatica/mediasoup-client@3.24.0...3.24.1

3.24.0

Full Changelog: versatica/mediasoup-client@3.23.2...3.24.0

3.23.2

What's Changed

New Contributors

Full Changelog: versatica/mediasoup-client@3.23.1...3.23.2

Commits

Updates react-router-dom from 7.18.3 to 7.18.4

Changelog

Sourced from react-router-dom's changelog.

v7.18.4

Patch Changes

Commits

Updates socket.io-client from 4.8.3 to 4.8.4

Release notes

Sourced from socket.io-client's releases.

socket.io-client@4.8.4

Bug Fixes

  • types: export ExtendedError for connect_error event (#5548) (c0d5450)
  • types: export reserved event interfaces (#5533) (03945df)

Dependencies

Commits
  • 11a6f56 chore(release): socket.io-client@4.8.4
  • 00e4e73 chore(release): engine.io-client@6.6.7
  • e387ab1 chore: use @​rollup/plugin-terser instead of rollup-plugin-terser
  • 9738333 chore(release): engine.io@6.6.11
  • fc9dd90 docs(eio): rework README
  • da008a5 fix(eio): refresh ping timeout on incoming packets
  • 3df3fed fix(eio-client): restore default transport resolution
  • aaf2af3 test: upgrade WebdriverIO to v9
  • b5da079 refactor(sio): simplify packet handling switch
  • 45873ca docs(protocol): clarify namespace comma restriction for built-in parser (#5545)
  • Additional commits viewable in compare view

Updates tailwind-merge from 3.6.0 to 3.7.0

Release notes

Sourced from tailwind-merge's releases.

tailwind-merge@3.7.0

New Features

  • Prepare some upcoming changes by @​dcastil in dcastil/tailwind-merge#713
    • Theme getters returned by fromTheme now expose the theme key they read as a themeKey property, so tooling can identify the referenced theme scale without calling the getter.
    • Release tags now include the package name, starting with tailwind-merge@3.7.0.

Bug Fixes

Documentation

Other

Full Changelog: v3.6.0...v3.7.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, a private sponsor, @​openclaw, @​sourcegraph, @​cesarvcanal, @​CasperKristiansson, @​jbisasky, @​frontendmasters and more via @​thnxdev for sponsoring tailwind-merge! ❤️

Commits
  • 511d68a tailwind-merge@3.7.0
  • 2461127 Release tooling: Pass the namespaced tag prefix and commit message to pnpm's ...
  • 9d41508 add changelog for tailwind-merge@3.7.0
  • c78a80f Configurator: Reuse runtime lookups during pruning
  • 49c317d Monorepo: Fix contributing link and include package coverage
  • 7b565ca Configurator: prune a generated config to a project's used classes (core step)
  • d83e013 Releases: auto-re-pin tag-pinned links on every version bump
  • b71fd41 Docs: pin every in-repo file link to a release tag instead of main
  • ee29441 Docs: point the ThemeObject JSDoc link at the packaged docs location
  • 9521b10 Releases: per-package pipeline with namespaced tags
  • Additional commits viewable in compare view

Updates web-vitals from 6.2.1 to 6.2.2

Changelog

Sourced from web-vitals's changelog.

v6.2.2 (2026-09-14)

  • Cap pending LoAFs to avoid memory leak (#796)
Commits

Updates @aws-amplify/backend from 1.24.1 to 1.25.1

Release notes

Sourced from @​aws-amplify/backend's releases.

@​aws-amplify/backend@​1.25.1

Patch Changes

  • 71f6e18: Bump @aws-amplify/backend alongside the @aws-amplify/backend-auth manageProviderForUser change so the umbrella package stays version-consistent with its sub-dependencies (satisfies check_changeset_completeness).
  • Updated dependencies [3231b13]
  • Updated dependencies [d3b0a79]
    • @​aws-amplify/platform-core@​1.12.1
    • @​aws-amplify/backend-auth@​1.10.1

@​aws-amplify/backend@​1.25.0

Minor Changes

  • 02be24d: feat: standalone SSR hosting & CI/CD for Gen 2
    • defineHosting (@aws-amplify/hosting) — framework-agnostic SSR/SSG (Next.js, Nuxt/Nitro, Astro, SPA) on CloudFront + Lambda via an OpenNext build (KVS edge routing, ISR cache seeding, image optimization, multi-domain/WAF, cache/headers, skew protection), built on @aws-blocks/hosting 0.3.0.
    • definePipeline (@aws-amplify/hosting/pipeline) — a self-mutating CodePipeline (one per branch) with a two-phase backend-then-hosting deploy and typed per-stage config, built on @aws-blocks/pipeline 0.2.1.
    • Self-managed values — secret() (AWS Secrets Manager) / config() (SSM Parameter Store) in defineHosting's environment, read at runtime with getSecret/getConfig from the CDK-free @aws-amplify/hosting/runtime entry; byoSecret()/byoConfig() reference existing entries with no user CDK. Only the store locator is injected into compute — never the value; namespaces default to /amplify/hosting/<project>/{secrets,config}.
    • CLI — ampx deploy gains --backend/--frontend and defaults --identifier to the sanitized package.json name; new ampx secret / ampx config (set/get/list/remove) manage self-managed hosting values.

Patch Changes

  • Updated dependencies [02be24d]
  • Updated dependencies [a0421b3]
    • @​aws-amplify/backend-data@​1.9.0
    • @​aws-amplify/backend-storage@​1.6.0
    • @​aws-amplify/platform-core@​1.12.0
    • @​aws-amplify/backend-auth@​1.10.0
    • @​aws-amplify/backend-function@​1.19.0
    • @​aws-amplify/backend-output-storage@​1.4.0
    • @​aws-amplify/client-config@​1.11.1
    • @​aws-amplify/plugin-types@​1.13.0
Commits
  • 756275e Version Packages (#3342)
  • 3550683 fix(backend-deployer): decouple internal type-check from project TypeScript v...
  • 3231b13 fix(platform-core): reject prototype-polluting keys in config path walk (#3350)
  • 5274ccf fix(integration-tests): allow @​aws-amplify/hosting build scripts in pnpm e2e ...
  • 08e0d49 fix(seed): restore caret range for aws-amplify to allow dedup (#3323) (#3339)
  • 70960e8 fix(e2e-cleanup): fail-closed CloudFront origin guard + broaden S3 origin mat...
  • 71f6e18 fix(changeset): bump @​aws-amplify/backend to match backend-auth sub-dependenc...
  • d3b0a79 Add AdminLinkProviderForUser action to manageUsers ActionMap (#3075)
  • ef46c66 fix(backend-deployer): map toolkit-lib countAssemblyResults crash to a fault ...
  • cb7aa4c fix(create-amplify): exit quietly when a prompt is cancelled with ctrl+c (#3291)
  • Additional commits viewable in compare view

Updates @aws-amplify/backend-cli from 1.9.1 to 1.10.0

Release notes

Sourced from @​aws-amplify/backend-cli's releases.

@​aws-amplify/backend-cli@​1.10.0

Minor Changes

  • 02be24d: feat: standalone SSR hosting & CI/CD for Gen 2
    • defineHosting (@aws-amplify/hosting) — framework-agnostic SSR/SSG (Next.js, Nuxt/Nitro, Astro, SPA) on CloudFront + Lambda via an OpenNext build (KVS edge routing, ISR cache seeding, image optimization, multi-domain/WAF, cache/headers, skew protection), built on @aws-blocks/hosting 0.3.0.
    • definePipeline (@aws-amplify/hosting/pipeline) — a self-mutating CodePipeline (one per branch) with a two-phase backend-then-hosting deploy and typed per-stage config, built on @aws-blocks/pipeline 0.2.1.
    • Self-managed values — secret() (AWS Secrets Manager) / config() (SSM Parameter Store) in defineHosting's environment, read at runtime with getSecret/getConfig from the CDK-free @aws-amplify/hosting/runtime entry; byoSecret()/byoConfig() reference existing entries with no user CDK. Only the store locator is injected into compute — never the value; namespaces default to /amplify/hosting/<project>/{secrets,config}.
    • CLI — ampx deploy gains --backend/--frontend and defaults --identifier to the sanitized package.json name; new ampx secret / ampx config (set/get/list/remove) manage self-managed hosting values.

Patch Changes

  • Updated dependencies [02be24d]
  • Updated dependencies [a0421b3]
    • @​aws-amplify/backend-deployer@​2.3.0
    • @​aws-amplify/hosting@​1.0.0
    • @​aws-amplify/platform-core@​1.12.0
    • @​aws-amplify/cli-core@​2.2.7
    • @​aws-amplify/client-config@​1.11.1
    • @​aws-amplify/deployed-backend-client@​1.8.3
    • @​aws-amplify/form-generator@​1.2.8
    • @​aws-amplify/model-generator@​1.2.5
    • @​aws-amplify/plugin-types@​1.13.0
    • @​aws-amplify/sandbox@​2.3.1
Commits
  • f60180a Version Packages (#3330)
  • 1e3ee35 fix(scripts): handle symbol-brand keys in check_api_changes (#3338)
  • 02be24d feat: standalone SSR hosting & CI/CD for Amplify Gen 2 (defineHosting / defin...
  • 04e03a9 fix(scripts): allow @​aws-amplify/backend-notifications 2.x in check_package_v...
  • a0421b3 fix(backend): migrate CfnResource#addDependency to addResourceDependency (dep...
  • See full diff in compare view

Updates aws-cdk-lib from 2.268.0 to 2.271.0

Release notes

Sourced from aws-cdk-lib's releases.

v2.271.0

Features

Bug Fixes

  • core: upgrade CloudFormation validation to latest version (#38884) (0c5e732)
  • ecs: support digest references in TagParameterContainerImage via imageDigest option (#37868) (f482f4f), closes #37718
  • ssm secret.fromSsmParameter introduces W2001 warning (#38833) (9526219), closes #38396
  • telemetry numbers don't allow making a good model for synth time yet (#38889) (600ffc8)
  • validating CloudAssembly throws Invalid URL error (#38867) (6eb07dd)
  • cloudwatch: iqm alarms are not rendered correctly (#38834) (7f714ce), closes #28812
  • core: resolveReferences should only update references that require updates on its second pass in nested stacks (#38813) (6cf5313)
  • core: acknowledgeWarning before emit on same construct is ignored (#38821) (e840b92), closes #38820
  • core: validations.acknowledge() does not respect scopes (#38789) (2f32847), closes #38495
  • ec2: synth-time AMI lookup leads to W9010 (#38840) (0870fcf), closes #38390

Alpha modules (2.271.0-alpha.0)

v2.270.0

⚠ BREAKING CHANGES

  • ** L1 resources are automatically generated from public CloudFormation Resource Schemas. They are built to closely reflect the real state of CloudFormation. Sometimes these updates can contain changes that are incompatible with previous types, but more accurately reflect reality. In this release we have changed:

    aws-codecommit: AWS::CodeCommit::Repository: Id attribute removed. aws-config: AWS::Config::DeliveryChannel: DeliveryFrequency property values narrowed to an enum. aws-dms: AWS::DMS::ReplicationTask: Id attribute removed.

Features

  • update L1 CloudFormation resource definitions (#38823) (4386bf1)
  • core: add cross-resource GameLift launch-path rules (CDK-GameLift-006/007) (ba98771)
  • core: merge default Rego rules into explicitly registered plugins (160c8a6)
  • core: replace schema-covered Rego rules with cross-field invariants (07a8153)
  • core: ship default CloudFormation validation rules in Rego (5388c88)
  • core: ship default CloudFormation validation rules in Rego (#38448) (4ccdad8), closes #38456
  • glue: graduate to stable 🚀 (#38799) (a9e36a3)
  • lambda: add DirectS3Read support for S3 Files filesystem mounts (#38752) (1482712), closes #38751

Bug Fixes

  • apigatewayv2: missing WebSocket Lambda permissions for routes sharing one integration (#38154) (4317f8e), closes #38148

... (truncated)

Changelog

Sourced from aws-cdk-lib's changelog.

Changelog

All notable changes to this project will be documented in this file. See standard-version for commit guidelines.

2.272.0-alpha.0 (2026-09-30)

2.271.0-alpha.0 (2026-09-25)

2.270.0-alpha.0 (2026-09-17)

2.269.0-alpha.0 (2026-09-10)

⚠ BREAKING CHANGES

  • glue-alpha: Glue job constructs now reject construct-managed and Glue-reserved arguments passed through defaultArguments. Previously, a managed argument set via defaultArguments was silently honored in SparkJob and PythonShellJob (customer value won over the construct default) and silently ignored in RayJob (construct default won). Both behaviors let a caller bypass the construct's security and observability defaults with no error. Passing any of the following through defaultArguments now throws a ValidationError at synthesis time:
  • construct-managed arguments — --enable-continuous-cloudwatch-log, --continuous-log-logGroup, --continuous-log-logStreamPrefix, --continuous-log-conversionPattern, --enable-continuous-log-filter, --enable-metrics, --enable-observability-metrics, --enable-spark-ui, --spark-event-logs-path, --job-language, --class, --extra-jars, --user-jars-first, --extra-py-files, --extra-files, library-set
  • Glue-reserved arguments — --debug, --mode, --JOB_NAME, --endpoint

A managed argument is rejected whether or not the current configuration emits it, so a disabled feature (e.g. enableMetrics: false) cannot be re-enabled through defaultArguments. Configure these through their dedicated props instead (continuousLogging, enableMetrics, enableObservabilityMetrics, sparkUI, className, extraJars, extraJarsFirst, extraPythonFiles, extraFiles). For example, replace defaultArguments: { '--enable-continuous-cloudwatch-log': 'false' } with continuousLogging: { enabled: false }. Arguments without a dedicated prop (e.g. --enable-glue-datacatalog) are unaffected and remain settable via defaultArguments.

The checkNoReservedArgs(defaultArguments?) method on the Job base class was removed. It is replaced by two protected members: setManagedArgument(key, value?), which each job class calls to declare (and, when a value is present, emit) a managed argument, and mergeDefaultArguments(defaultArguments?), which validates the caller-supplied defaultArguments against the accumulated reserved set and returns the merged map.

  • route53resolver-alpha: FirewallRuleGroupAssociation now honors the previously-ignored mutationProtection and name props. Stacks that set mutationProtection: true will enable mutation protection on redeploy (which blocks further CloudFormation update/delete until it is set back to false); stacks that set name will write it to the template, which may replace the association.
  • glue-alpha: trigger Action and Condition are no longer plain objects — use Action.job(...) / Action.crawler(...) and Condition.job(...) / Condition.crawler(...). Jobs are referenced via IJobRef and crawlers via ICrawlerRef (a CfnCrawler instance or CfnCrawler.fromCrawlerName(...)) instead of a CfnCrawler field or crawler-name string; IJob now extends the generated IJobRef. addDailyScheduledTrigger/addWeeklyScheduledTrigger/addCustomScheduledTrigger are replaced by addScheduledTrigger(id, { schedule, ... }) (use TriggerSchedule.daily()/weekly()/cron(...)). addNotifyEventTrigger is renamed addEventTrigger (NotifyEventTriggerOptions → EventTriggerOptions). All addXxxTrigger methods now return ITriggerRef instead of CfnTrigger.
  • glue-alpha: PartitionProjectionConfiguration's variant fields (integerRange, dateRange, interval, digits, format, intervalUnit, values) are no longer public; DATE projection now takes step: { interval, intervalUnit } instead of top-level interval/intervalUnit.
  • glue-alpha: ConnectionOptions no longer has subnet, vpc, or vpcSubnets; use network: ConnectionNetwork.subnet(...) or network: ConnectionNetwork.vpc(...) instead.

Features

... (truncated)

Commits
  • e79e753 chore: update analytics metadata blueprints
  • 0c5e732 fix(core): upgrade CloudFormation validation to latest version (#38884)
  • f482f4f fix(ecs): support digest references in TagParameterContainerImage via imageDi...
  • 600ffc8 fix: telemetry numbers don't allow making a good model for synth time yet (#3...

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 29, 2026
@dependabot
Bump the frontend-minor-patch group across 1 directory with 14 updates
1bc1eee 
Bumps the frontend-minor-patch group with 14 updates in the /frontend directory:

| Package | From | To |
| --- | --- | --- |
| [aws-amplify](https://github.com/aws-amplify/amplify-js/tree/HEAD/packages/aws-amplify) | `6.20.0` | `6.22.0` |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `1.44.0` | `1.48.0` |
| [mediasoup-client](https://github.com/versatica/mediasoup-client) | `3.23.1` | `3.24.1` |
| [react-router-dom](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom) | `7.18.3` | `7.18.4` |
| [socket.io-client](https://github.com/socketio/socket.io) | `4.8.3` | `4.8.4` |
| [tailwind-merge](https://github.com/dcastil/tailwind-merge/tree/HEAD/packages/tailwind-merge) | `3.6.0` | `3.7.0` |
| [web-vitals](https://github.com/GoogleChrome/web-vitals) | `6.2.1` | `6.2.2` |
| [@aws-amplify/backend](https://github.com/aws-amplify/amplify-backend) | `1.24.1` | `1.25.1` |
| [@aws-amplify/backend-cli](https://github.com/aws-amplify/amplify-backend) | `1.9.1` | `1.10.0` |
| [aws-cdk-lib](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk-lib) | `2.268.0` | `2.271.0` |
| [eslint-plugin-react-refresh](https://github.com/ArnaudBarre/eslint-plugin-react-refresh) | `0.5.6` | `0.5.7` |
| [tsx](https://github.com/privatenumber/tsx) | `4.23.13` | `4.23.15` |
| [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.70.0` | `8.70.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.2.2` | `8.3.1` |



Updates `aws-amplify` from 6.20.0 to 6.22.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.22.0/packages/aws-amplify)

Updates `lucide-react` from 1.44.0 to 1.48.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.48.0/packages/lucide-react)

Updates `mediasoup-client` from 3.23.1 to 3.24.1
- [Release notes](https://github.com/versatica/mediasoup-client/releases)
- [Commits](versatica/mediasoup-client@3.23.1...3.24.1)

Updates `react-router-dom` from 7.18.3 to 7.18.4
- [Release notes](https://github.com/remix-run/react-router/releases)
- [Changelog](https://github.com/remix-run/react-router/blob/react-router-dom@7.18.4/packages/react-router-dom/CHANGELOG.md)
- [Commits](https://github.com/remix-run/react-router/commits/react-router-dom@7.18.4/packages/react-router-dom)

Updates `socket.io-client` from 4.8.3 to 4.8.4
- [Release notes](https://github.com/socketio/socket.io/releases)
- [Changelog](https://github.com/socketio/socket.io/blob/main/CHANGELOG.md)
- [Commits](https://github.com/socketio/socket.io/compare/socket.io-client@4.8.3...socket.io-client@4.8.4)

Updates `tailwind-merge` from 3.6.0 to 3.7.0
- [Release notes](https://github.com/dcastil/tailwind-merge/releases)
- [Commits](https://github.com/dcastil/tailwind-merge/commits/tailwind-merge@3.7.0/packages/tailwind-merge)

Updates `web-vitals` from 6.2.1 to 6.2.2
- [Changelog](https://github.com/GoogleChrome/web-vitals/blob/main/CHANGELOG.md)
- [Commits](GoogleChrome/web-vitals@v6.2.1...v6.2.2)

Updates `@aws-amplify/backend` from 1.24.1 to 1.25.1
- [Release notes](https://github.com/aws-amplify/amplify-backend/releases)
- [Commits](https://github.com/aws-amplify/amplify-backend/compare/@aws-amplify/backend@1.24.1...@aws-amplify/backend@1.25.1)

Updates `@aws-amplify/backend-cli` from 1.9.1 to 1.10.0
- [Release notes](https://github.com/aws-amplify/amplify-backend/releases)
- [Commits](https://github.com/aws-amplify/amplify-backend/compare/@aws-amplify/backend-cli@1.9.1...@aws-amplify/backend-cli@1.10.0)

Updates `aws-cdk-lib` from 2.268.0 to 2.271.0
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/main/CHANGELOG.v2.alpha.md)
- [Commits](https://github.com/aws/aws-cdk/commits/v2.271.0/packages/aws-cdk-lib)

Updates `eslint-plugin-react-refresh` from 0.5.6 to 0.5.7
- [Release notes](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/releases)
- [Changelog](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/main/CHANGELOG.md)
- [Commits](ArnaudBarre/eslint-plugin-react-refresh@v0.5.6...v0.5.7)

Updates `tsx` from 4.23.13 to 4.23.15
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.23.13...v4.23.15)

Updates `typescript-eslint` from 8.70.0 to 8.70.1
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.70.1/packages/typescript-eslint)

Updates `vite` from 8.2.2 to 8.3.1
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.3.1/packages/vite)

---
updated-dependencies:
- dependency-name: "@aws-amplify/backend"
  dependency-version: 1.25.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@aws-amplify/backend-cli"
  dependency-version: 1.10.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: aws-amplify
  dependency-version: 6.22.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: aws-cdk-lib
  dependency-version: 2.271.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: eslint-plugin-react-refresh
  dependency-version: 0.5.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: lucide-react
  dependency-version: 1.48.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: mediasoup-client
  dependency-version: 3.24.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: react-router-dom
  dependency-version: 7.18.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: socket.io-client
  dependency-version: 4.8.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: tailwind-merge
  dependency-version: 3.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: tsx
  dependency-version: 4.23.15
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: typescript-eslint
  dependency-version: 8.70.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: vite
  dependency-version: 8.3.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: web-vitals
  dependency-version: 6.2.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/frontend/frontend-minor-patch-f50e9da337 branch from dc22cb2 to 1bc1eee Compare October 1, 2026 03:16
@dependabot @github

dependabot Bot commented on behalf of github Oct 8, 2026

Copy link
Copy Markdown
Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 8, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/frontend/frontend-minor-patch-f50e9da337 branch October 8, 2026 03:11
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