build(deps): bump the minor-and-patch group across 1 directory with 14 updates
Type: Pull Request
State: Open
Association: Unknown
Comments: 1
(7 days ago)
(7 days ago)
Bumps the minor-and-patch group with 14 updates in the /frontend directory:
| Package | From | To |
|---|---|---|
| @tanstack/react-query | 5.100.10 |
5.101.0 |
| @tanstack/react-query-devtools | 5.100.10 |
5.101.0 |
| axios | 1.16.0 |
1.17.0 |
| dayjs | 1.11.20 |
1.11.21 |
| dompurify | 3.4.2 |
3.4.8 |
| @types/dompurify | 3.0.5 |
3.2.0 |
| lucide-react | 1.16.0 |
1.17.0 |
| tailwind-merge | 3.5.0 |
3.6.0 |
| zustand | 5.0.13 |
5.0.14 |
| esbuild | 0.27.7 |
0.28.0 |
| eslint-plugin-react-refresh | 0.4.26 |
0.5.2 |
| lint-staged | 17.0.4 |
17.0.7 |
| postcss | 8.5.13 |
8.5.15 |
| sass | 1.99.0 |
1.100.0 |
Updates @tanstack/react-query from 5.100.10 to 5.101.0
Release notes
Sourced from @tanstack/react-query's releases.
@tanstack/react-query-devtools@5.101.0Patch Changes
@tanstack/react-query-next-experimental@5.101.0Patch Changes
#10857
7cf5923- fix(react-query-next-experimental): replace deprecated 'isServer' with 'environmentManager.isServer()'Updated dependencies []:
@tanstack/react-query@5.101.0
@tanstack/react-query-persist-client@5.101.0Patch Changes
- Updated dependencies []:
@tanstack/react-query@5.101.0Patch Changes
- Updated dependencies []:
@tanstack/query-core@5.101.0
@tanstack/react-query-devtools@5.100.14Patch Changes
- Updated dependencies [
ed20b6d]:
@tanstack/react-query-next-experimental@5.100.14Patch Changes
@tanstack/react-query-persist-client@5.100.14Patch Changes
- Updated dependencies [
ed20b6d]:
@tanstack/react-query@5.100.14Patch Changes
... (truncated)
Changelog
Sourced from @tanstack/react-query's changelog.
5.101.0
Patch Changes
- Updated dependencies []:
@tanstack/query-core@5.101.05.100.14
Patch Changes
fix(react-query): do not go into optimistic fetching state when not subscribed (#10759)
Updated dependencies []:
@tanstack/query-core@5.100.145.100.13
Patch Changes
5.100.12
Patch Changes
- Updated dependencies []:
@tanstack/query-core@5.100.125.100.11
Patch Changes
- Updated dependencies []:
@tanstack/query-core@5.100.11
Commits
- See full diff in compare view
Updates @tanstack/react-query-devtools from 5.100.10 to 5.101.0
Release notes
Sourced from @tanstack/react-query-devtools's releases.
@tanstack/react-query-devtools@5.101.0Patch Changes
@tanstack/react-query-devtools@5.100.14Patch Changes
- Updated dependencies [
ed20b6d]:
@tanstack/react-query-devtools@5.100.13Patch Changes
@tanstack/react-query-devtools@5.100.12Patch Changes
Changelog
Sourced from @tanstack/react-query-devtools's changelog.
5.101.0
Patch Changes
5.100.14
Patch Changes
- Updated dependencies [
ed20b6d]:5.100.13
Patch Changes
5.100.12
Patch Changes
5.100.11
Patch Changes
Commits
- See full diff in compare view
Updates axios from 1.16.0 to 1.17.0
Release notes
Sourced from axios's releases.
v1.17.0 — June 1, 2026
This release adds Node HTTP zstd decompression, hardens config and release workflows, and fixes authentication, header, proxy, and type-handling regressions.
🔒 Security Fixes
- Config Hardening: Guarded
socketPath,params, andparamsSerializerreads with own-property checks to prevent inherited prototype values from affecting request behavior, including SSRF-sensitive paths. (#10901, #10922)- Release Publishing: Switched the publish workflow to npm staged publishing for safer, auditable package releases with provenance. (#10926)
🚀 New Features
- HTTP Compression: Added Node HTTP adapter support for zstd response decompression, with
transitional.advertiseZstdAcceptEncodingcontrolling whetherzstdis advertised inAccept-Encoding. (#6792, #10920)🐛 Bug Fixes
- Authentication Handling: Restored Basic auth on same-origin Node redirects while continuing to strip credentials cross-origin, and aligned the fetch adapter with HTTP adapter behavior for URL-embedded Basic auth. (#10929, #10896)
- Proxy TLS: Preserved user
httpsAgentTLS options when tunneling HTTPS requests through HTTP CONNECT proxies. (#10957)- React Native FormData: Cleared default
Content-Typefor React NativeFormDataso multipart boundaries can be generated correctly. (#10898)- Headers: Silently skipped empty or whitespace-only header names instead of throwing, matching parsed-header behavior and avoiding React Native response crashes. (#10875)
- Request Data Merging: Preserved enumerable symbol keys when cloning plain request data through axios merge logic. (#10812)
- Bundler Compatibility: Converted
resolveConfigfrom an arrow default export to a named function export to avoid webpack and Babel transform interop failures. (#10891)- Types: Corrected
AxiosHeaders.toJSON()return types and updated CommonJSisCanceltypings to narrow toCanceledError<T>. (#10956, #10952)- Build Tooling: Avoided emitting a null
Authorizationheader from the GitHub build helper whenGITHUB_TOKENis unset. (#10931)🔧 Maintenance & Chores
- HTTP/2 Internals: Extracted
Http2Sessionsinto its own helper module and added direct unit coverage for session pooling, timeout, and cleanup behavior. (#10861)- Package Publishing: Reduced published package size by switching to a
filesallowlist and dropping unneeded unminified bundle source maps. (#10939)- CI and Release Automation: Added bundle-size reporting, moved reports to the job summary, fixed bundle-size comparison coverage, added Node 26 to the matrix, pinned npm for staged publishing, and prepared the 1.17.0 release. (#10907, #10911, #10916, #10927, #10935, #10983)
- Developer Workflow: Added a dev container and iterated on OpenSpec workflow files before removing them from the release branch. (#10925, #10914, #10958)
- Documentation and Policy: Updated disclosure, contributor, collaboration, threat-model, advanced docs, README badges, release notes, moderator configuration, and project metadata. (#10890, #10889, #10921, #10945, #10905, #10933, #10915, #10887, #10955)
- Dependencies: Bumped Babel tooling, Commitlint, ESLint, Rollup, Globals, Vitest, Playwright,
fs-extra,qs, docs dependencies, and GitHub Actions dependencies includingactions/dependency-review-actionandzizmorcore/zizmor-action. (#10871, #10879, #10918, #10919, #10934, #10947, #10954, #10960)🌟 New Contributors
We are thrilled to welcome our new contributors. Thank you for helping improve axios:
... (truncated)
Changelog
Sourced from axios's changelog.
Changelog
v1.16.1 — May 13, 2026
This release ships a defence-in-depth fix for prototype pollution in
formDataToJSON, hardens proxy and CI workflows, restores Webpack 4 compatibility for the fetch adapter, and includes several small bug fixes and maintenance improvements.🔒 Security Fixes
- Prototype Pollution Defence-in-Depth: Hardened
formDataToJSONagainst already-pollutedObject.prototypeby walking own properties only, so attacker-controlled keys inherited from a poisoned prototype cannot propagate through deserialization. (#7413)- Proxy Cleartext Leak: Fixed an issue where HTTPS request data could be transmitted in cleartext to an HTTP proxy under certain configurations. (#10858)
- CI Cache Removal: Removed all GitHub Actions caches as a defence-in-depth measure against cache poisoning vectors in the build pipeline. (#10882)
🐛 Bug Fixes
- Data URI Parsing: Updated the
fromDataURIregex to match RFC 2397 more strictly, fixing edge cases indata:URL handling. (#10829)- Unicode Headers: Preserved Unicode header values when running through request interceptors, so non-ASCII header content is no longer corrupted before dispatch. (#10850)
- XHR Upload Progress: Guarded against malformed
ProgressEventpayloads emitted by some environments during XHR upload, preventing crashes whenloaded/totalare missing or invalid. (#10868)- Webpack 4 Fetch Adapter: Fixed an "unexpected token" error caused by syntax in the fetch adapter that Webpack 4 could not parse, restoring compatibility for legacy bundler users. (#10864)
- Type Definitions: Made
parseRevivercontext.sourceoptional in the type definitions to align with the ES2023 specification. (#10837)- URL Object Support Reverted: Reverted the change that allowed passing a
URLobject asconfig.url(originally #10866) due to regressions; this support will be reintroduced in a later release once the underlying issues are addressed. (#10874)🔧 Maintenance & Chores
- Cycle Detection Refactor: Replaced the array-based cycle tracker in
toJSONObjectwith aWeakSet, improving performance and memory behaviour on large nested structures. (#10832)- composeSignals Cleanup: Refactored
composeSignalsto use a clearer early-return structure, simplifying the cancellation/abort composition path. (#10844)- AI Readiness & Repo Docs: Added
AGENTS.mdand related contributor-guide updates for both human and AI agents, plus post-release documentation improvements. (#10835, #10841)- Docs Improvements: Clarified the GET request example, fixed the interceptor
ejectexample to reference the correct instance, and corrected the Buzzoid sponsor description in the README. (#10836, #10853, #10856)- Sponsorship Tooling: Fixed empty sponsor arrays in the sponsor processing script, added the ability to inject additional sponsors, updated the sponsorship link, and added a Twicsy advertisement entry. (#10843, #10859, #10869)
- Dependencies: Bumped
@commitlint/clifrom 20.5.0 to 20.5.2. (#10846)🌟 New Contributors
We are thrilled to welcome our new contributors. Thank you for helping improve axios:
Commits
4306df2chore: add fun 88 sponsorship931cc8fchore(release): prepare release 1.17.0 (#10983)38ba1b3fix(fetch): support basic auth from URL (#10896)32e2515fix: replace ternary side effect in script (#10931)030e722chore(deps): bump axios from 1.15.2 to 1.16.1 in /docs (#10960)ec63164chore: remove openspec (#10958)3dec28ffix(http): preserve TLS options for proxy tunnels (#10957)a2390a5fix: correct isCancel type to narrow to CanceledError<T> (#10952)fa01b92chore(deps-dev): bump tmp from 0.2.5 to 0.2.7 in /docs (#10954)2d2314afix: AxiosHeaderstoJSON()return types (#10956)- Additional commits viewable in compare view
Updates dayjs from 1.11.20 to 1.11.21
Commits
a25f01echore(release): 1.11.21 [skip ci]ee75cc2Merge pull request #3113 from iamkun/dev1a8bf27chore: update doc51ef048chore: support window os test execution using cross-env (#3064)7bb06f8chore: add download chart (#3045)f6d72cedocs: fix documentation (#3044)dcae6d7chore: update docb84592fchore: update docea2929dchore: update doc523007dchore: update doc- Additional commits viewable in compare view
Updates dompurify from 3.4.2 to 3.4.8
Release notes
Sourced from dompurify's releases.
DOMPurify 3.4.8
- Cleaned up the repository root, renamed some and removed unneeded files
- Fixed an issue with handling of Trusted Types policies, thanks
@fulstadev- Fixed the node iterator for better template scrubbing, thanks
@IamLeandrooooo- Included formerly missing LICENSE-MPL in published npm package, thanks
@asamuzaK- Bumped several dependencies where possible
DOMPurify 3.4.7
- Hardened the handling of Shadow Roots when using
IN_PLACE, thanks@GameZoneHacker- Removed a problem leading to permanent hook pollution, thanks
@offset- Refactored the test suite and expanded test coverage significantly
DOMPurify 3.4.6
- Fixed several issues with DOM Clobbering in
IN_PLACEmode, thanks@offset&@Bankde- Hardened the checks for cross-realm
IN_PLACEand Shadow DOM sanitization, thanks@offset&@Bankde- Added more test coverage for
IN_PLACEand general DOM Clobbering attacks- Bumped several dependencies where possible
DOMPurify 3.4.5
- Fixed a bypass caused by the new HTML element
selectedcontentadded in 3.4.4, thanks@KabirAcharyaNote that this is a security release for an issue introduced in 3.4.4 and should be upgraded to immediately.
DOMPurify 3.4.4
- Added the
selectedcontentelement to default allow-list, thanks@lukewarlow- Added the
commandandcommandforattributes to default allowed-list, thanks@lukewarlow- Added better template scrubbing for
IN_PLACEoperations, thanks@DEMON1A- Added stronger checks for cross-realm windows, thanks
@DEMON1A&@fg0x0- Updated demo website and made sure it uses the latest from main
- Updated existing workflows, fuzzer, dependabot, etc., added more tests
- Bumped several dependencies where possible
🚨 This release had been flagged as deprecated, please use DOMPurify 3.4.5 instead 🚨
DOMPurify 3.4.3
- Fixed an issue with handling of nested Shadow DOM trees, thanks
@fishjojo1- Fixed the template regexes to be more robust against ReDoS attacks, thanks
@aleung27- Updated the node iteration code to catch more Shadow DOM related issues
- Updated Playwright and added Node 26 to test matrix
- Updated existing workflows, fuzzer, release signing, etc., added more tests
- Bumped several dependencies where possible
Commits
Updates @types/dompurify from 3.0.5 to 3.2.0
Commits
- See full diff in compare view
Updates lucide-react from 1.16.0 to 1.17.0
Release notes
Sourced from lucide-react's releases.
Version 1.17.0
What's Changed
- chore(lucide-vue-next|lucide-svelte|lucide-angular): Remove deprecated packages by
@ericfennisin lucide-icons/lucide#4376- chore(repo): Update issue templates and documentation for package ren… by
@ericfennisin lucide-icons/lucide#4379- feat(site): Adds survey overlay to website by
@ericfennisin lucide-icons/lucide#4380- feat(site): Certificate dev links by
@ericfennisin lucide-icons/lucide#4390- fix(icons): changed
martiniicon by@jamiemlawin lucide-icons/lucide#4335- chore(deps): bump brace-expansion from 1.1.11 to 5.0.6 by
@dependabot[bot] in lucide-icons/lucide#4386- chore(deps): bump
@tootallnate/oncefrom 2.0.0 to 2.0.1 by@dependabot[bot] in lucide-icons/lucide#4404- chore(deps): bump devalue from 5.8.0 to 5.8.1 by
@dependabot[bot] in lucide-icons/lucide#4391- chore(deps): bump ws from 8.18.0 to 8.20.1 by
@dependabot[bot] in lucide-icons/lucide#4392- fix(gh-icon): limit icon size to a maximum of 256 pixels by
@jguddasin lucide-icons/lucide#4398- chore(dependencies): Update dependencies by
@ericfennisin lucide-icons/lucide#4377- feat(copilot): Adding copilot instructions by
@ericfennisin lucide-icons/lucide#4407- feat(icons): add
globe-checkby@Barakudumin lucide-icons/lucide#4342- feat(metadata): Require use-cases in meta json by
@ericfennisin lucide-icons/lucide#4321- feat(icons): added
parasolicon by@karsa-mistmerein lucide-icons/lucide#4347Full Changelog: https://github.com/lucide-icons/lucide/compare/1.16.0...1.17.0
Commits
- See full diff in compare view
Updates tailwind-merge from 3.5.0 to 3.6.0
Release notes
Sourced from tailwind-merge's releases.
v3.6.0
New Features
- Add support for Tailwind CSS v4.3 by
@dcastilin dcastil/tailwind-merge#677
- Add
postfixLookupClassGroupsoption to config to support Tailwind utilities where a slash is part of the full class name, like named container queries- Add support for readonly array values by
@unionalin dcastil/tailwind-merge#652Documentation
- Fix broken links in README by
@maurer2in dcastil/tailwind-merge#662Other
- Harden internal CI pipeline security by omitting git checkout by
@dcastil, suggested by@kyletayloredin https://github.com/dcastil/tailwind-merge/commit/6b2499c10cf52bed42426d30b4219e90374b30d6Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v3.5.0...v3.6.0
Thanks to
@brandonmcconnell,@manavm1990,@langy,@roboflow,@syntaxfm,@getsentry,@codecov, a private sponsor,@block,@openclaw,@sourcegraph,@mike-healyand more via@thnxdevfor sponsoring tailwind-merge! ❤️
Commits
d54f7e5v3.6.0638871aUpdate README to add info about Tailwind CSS v4.3 support39fc7b5Revert "v3.6.0"bd8390fv3.6.0802877cadd v3.6.0 changeloga35fedaMerge pull request #665 from dcastil/renovate/rollup-plugin-babel-7.x940389cMerge pull request #667 from dcastil/renovate/release-drafter-release-drafter...005af6dpin to specific version5816cedimplement breaking changes17041e1Merge pull request #676 from dcastil/dependabot/npm_and_yarn/babel/plugin-tra...- Additional commits viewable in compare view
Updates zustand from 5.0.13 to 5.0.14
Release notes
Sourced from zustand's releases.
v5.0.14
This release fixes a type issue in devtools.
What's Changed
- fix(devtools): improve type inference for Devtools initializer by
@dbritto-devin pmndrs/zustand#3511New Contributors
@TheSeydiCharyyevmade their first contribution in pmndrs/zustand#3487@brofrongmade their first contribution in pmndrs/zustand#3496@hyun907made their first contribution in pmndrs/zustand#3506Full Changelog: https://github.com/pmndrs/zustand/compare/v5.0.13...v5.0.14
Commits
bfb2a9e5.0.1462b2affchore(deps): update dev dependencies (#3513)ad77bd3fix(devtools): improve type inference for Devtools initializer (#3511)8476d2cupdate pnpm etc (#3512)d690ec2docs(combine): add object constraints to T and U in signature (#3506)fd8c601docs(react): add Action constraint to redux middleware signature (#3492)2ce8226docs(immer): fix setPerson updater type in usage examples (#3502)038b938docs(updating-state): use curried create form with explicit state type (#3503)60a91b4docs(devtools): add missing devtools import to troubleshooting example (#3501)efad169Update FUNDING.json- Additional commits viewable in compare view
Updates esbuild from 0.27.7 to 0.28.0
Release notes
Sourced from esbuild's releases.
v0.28.0
Add support for
with { type: 'text' }imports (#4435)The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing
textloader. Here's an example:import string from './example.txt' with { type: 'text' } console.log(string)Add integrity checks to fallback download path (#4343)
Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the
npmcommand, and then with a HTTP request toregistry.npmjs.orgas a last resort).This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level
esbuildpackage. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.Update the Go compiler from 1.25.7 to 1.26.1
This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:
- It now uses the new garbage collector that comes with Go 1.26.
- The Go compiler is now more aggressive with allocating memory on the stack.
- The executable format that the Go linker uses has undergone several changes.
- The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.
You can read the Go 1.26 release notes for more information.
Changelog
Sourced from esbuild's changelog.
0.28.0
Add support for
with { type: 'text' }imports (#4435)The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing
textloader. Here's an example:import string from './example.txt' with { type: 'text' } console.log(string)Add integrity checks to fallback download path (#4343)
Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the
npmcommand, and then with a HTTP request toregistry.npmjs.orgas a last resort).This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level
esbuildpackage. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.Update the Go compiler from 1.25.7 to 1.26.1
This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:
- It now uses the new garbage collector that comes with Go 1.26.
- The Go compiler is now more aggressive with allocating memory on the stack.
- The executable format that the Go linker uses has undergone several changes.
- The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.
You can read the Go 1.26 release notes for more information.
Commits
6a794dfpublish 0.28.0 to npm64ee0eafix #4435: supportwith { type: text }importsef65aeefix sort order insnapshots_packagejson.txt1a26a8etry to fixtest-old-ts, also shuffle CI tasks556ce6cuse''instead ofnullto omit build hashes8e675a8ci: allow missing binary hashes for tests7067763Reapply "update go 1.25.7 => 1.26.1"39473a9fix #4343: integrity check for binary download- See full diff in compare view
Updates eslint-plugin-react-refresh from 0.4.26 to 0.5.2
Release notes
Sourced from eslint-plugin-react-refresh's releases.
v0.5.2
- Support nested function calls for extraHOCs (actually fixes #104)
v0.5.1
- Mark ESLint v10 as supported
- Support false positives with TypeScript function overloading (fixes #105)
- Support nested function calls for extraHOCs (fixes #104)
v0.5.0
Breaking changes
- The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
- A new
reactRefreshexport is available and prefered over the default export. It's an object with two properties:
plugin: The plugin object with the rulesconfigs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them with sensible defaults for that config, and return the final config object.customHOCsoption was renamed toextraHOCs- Validation of HOCs calls is now more strict, you may need to add some HOCs to the
extraHOCsoption (likeconnectorstyled)Config example:
import { defineConfig } from "eslint/config"; import { reactRefresh } from "eslint-plugin-react-refresh";export default defineConfig( /* Main config */ reactRefresh.configs.vite({ extraHOCs: ["someLibHOC"] }), );
Config example without config:
import { defineConfig } from "eslint/config"; import { reactRefresh } from "eslint-plugin-react-refresh";export default defineConfig({ files: ["/*.ts", "/*.tsx"], plugins: { // other plugins "react-refresh": reactRefresh.plugin, }, rules: { // other rules "react-refresh/only-export-components": [ "warn", { extraHOCs: ["someLibHOC"] }, ], }, }); </tr></table>
... (truncated)
Changelog
Sourced from eslint-plugin-react-refresh's changelog.
0.5.2
- Support nested function calls for extraHOCs (actually fixes #104)
0.5.1
- Mark ESLint v10 as supported
- Support false positives with TypeScript function overloading (fixes #105)
- Support nested function calls for extraHOCs (fixes #104)
0.5.0
Breaking changes
- The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
- A new
reactRefreshexport is available and prefered over the default export. It's an object with two properties:
plugin: The plugin object with the rulesconfigs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them wit...Description has been truncated
Package Dependencies
@tanstack/react-query-devtools
npm
5.100.10 → 5.101.0
Minor
eslint-plugin-react-refresh
npm
0.4.26 → 0.5.2
Minor
Technical Details
| ID: | 15987186 |
| UUID: | 4581276887 |
| Node ID: | PR_kwDOSRwQlc7iSp4B |
| Host: | GitHub |
| Repository: | MinhThang1009/E-commerce-website |