[release-4.21] maintenance: Bump the npm group across 1 directory with 24 updates

[dependabot]

Bumps the npm group with 24 updates in the / directory:

Package	From	To
sass	1.105.0	1.105.1
@peculiar/asn1-cms	2.9.5	2.10.0
@peculiar/asn1-csr	2.9.5	2.10.0
@peculiar/asn1-ecc	2.9.5	2.10.0
@peculiar/asn1-pfx	2.9.5	2.10.0
@peculiar/asn1-pkcs8	2.9.5	2.10.0
@peculiar/asn1-pkcs9	2.9.5	2.10.0
@peculiar/asn1-rsa	2.9.5	2.10.0
@peculiar/asn1-schema	2.9.5	2.10.0
@peculiar/asn1-x509	2.9.5	2.10.0
@peculiar/asn1-x509-attr	2.9.5	2.10.0
@types/d3-zoom	3.0.8	3.0.9
@types/ws	8.18.1	8.18.2
browserslist	4.28.7	4.29.3
baseline-browser-mapping	2.11.0	2.11.26
caniuse-lite	1.0.30001812	1.0.30001814
electron-to-chromium	1.5.439	1.5.444
enhanced-resolve	5.25.1	5.26.0
memfs	4.79.0	4.80.0
@parcel/watcher	2.5.1	2.6.0
detect-libc	1.0.3	2.1.2
shell-quote	1.10.0	1.12.0
systeminformation	5.33.13	5.33.15
webpack-sources	3.5.3	3.6.0

Updates sass from 1.105.0 to 1.105.1

Release notes

Sourced from sass's releases.

Dart Sass 1.105.1

To install Sass 1.105.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Improve error messages for @extends across different media queries.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.105.1

• Improve error messages for @extends across different media queries.

Commits

• db3c666 Merge pull request #2869 from sass/extend-media-errors
• 2ac4515 Improve span boundaries for media queries and selectors
• 706cfbf Fix InterpolationMap._expandInterpolationSpanRight()
• 792a948 Bump bufbuild/buf-action from 1.5.0 to 1.6.0 in /.github/util/initialize (#2870)
• 61ab702 Improve errors for @extend across media queries
• 288d4e2 Auto-merge dependabot PRs as the Sass bot account (#2866)
• See full diff in compare view

Updates @peculiar/asn1-cms from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-cms's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-csr from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-csr's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-ecc from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-ecc's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-pfx from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-pfx's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-pkcs8 from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-pkcs8's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-pkcs9 from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-pkcs9's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-rsa from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-rsa's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-schema from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-schema's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-x509 from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-x509's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @peculiar/asn1-x509-attr from 2.9.5 to 2.10.0

Release notes

Sourced from @​peculiar/asn1-x509-attr's releases.

v2.10.0

npm publish status

All intended npm packages were published successfully.

What's Changed

• fix: remove exports field for 2.x compatibility with 2.6 by @​microshine in PeculiarVentures/asn1-schema#161

Full Changelog: PeculiarVentures/asn1-schema@v2.9.5...v2.10.0

Commits

• 342632c chore(release): v2.10.0
• bc123f1 fix: remove exports field for 2.x compatibility with 2.6 resolution
• See full diff in compare view

Updates @types/d3-zoom from 3.0.8 to 3.0.9

Commits

• See full diff in compare view

Updates @types/ws from 8.18.1 to 8.18.2

Commits

• See full diff in compare view

Updates browserslist from 4.28.7 to 4.29.3

Release notes

Sourced from browserslist's releases.

4.29.3

• Updated Firefox ESR.

4.29.2

• Fixed ignoring null usage in cover X in Y query (by @​wahidrizka).

4.29.1

• Fixed config name loading protection on Windows (by @​oss-security-shop).
• Fixed case-insensitive negation queries (by @​jakezwang).
• Fixed percentage and supports queries case-insensitive (by @​wahidrizka).
• Fixed old Node.js tests (by @​aaron-belenky).
• Reduced code (by @​charmander).

4.29.0

• Added query continuations across lines and array entries (by @​fzlzjerry).

4.28.9

• Improve or parsing performance (by @​NotAFlightRisk).

4.28.8

• Fixed including kaios in baseline queries (by @​Jaybhade).

Changelog

Sourced from browserslist's changelog.

4.29.3

• Updated Firefox ESR.

4.29.2

• Fixed ignoring null usage in cover X in Y query (by @​wahidrizka).

4.29.1

• Fixed config name loading protection on Windows (by @​oss-security-shop).
• Fixed case-insensitive negation queries (by @​jakezwang).
• Fixed percentage and supports queries case-insensitive (by @​wahidrizka).
• Fixed old Node.js tests (by @​aaron-belenky).
• Reduced code (by @​charmander).

4.29.0

• Added query continuations across lines and array entries (by @​fzlzjerry).

4.28.9

• Improved or parsing performance (by @​NotAFlightRisk).

4.28.8

• Fixed including kaios in baseline queries (by @​Jaybhade).

Commits

• b4809dd Release 4.29.3 version
• 9d844f8 Update Firefox ESR
• 0033f34 Update dependencies
• 906d329 Release 4.29.2 version
• ff8c83f Update dependencies
• 067f4a1 Merge pull request #952 from wahidrizka/fix-cover-null-usage
• f760921 Do not add versions without usage data to cover queries
• 5be63f5 Merge pull request #953 from wahidrizka/docs-android-latest-version
• 1e5356f Note that Android version queries return only the latest version
• 5b7e941 Add missed changes to ChangeLog
• Additional commits viewable in compare view

Updates baseline-browser-mapping from 2.11.0 to 2.11.26

Commits

• c1934c6 Patch to 2.11.26 because browser or feature data changed
• 4873684 Browser or feature data changed
• 9030798 Updating static site
• a5df351 Updating static site
• ecc5b54 Updating static site
• 719bf7a Patch to 2.11.25 because browser or feature data changed
• c4f5b49 Browser or feature data changed
• aa194af Updating static site
• 0d33c4a Patch to 2.11.24 because browser or feature data changed
• 1dac891 Browser or feature data changed
• Additional commits viewable in compare view

Updates caniuse-lite from 1.0.30001812 to 1.0.30001814

Commits

• 663dbe9 Update caniuse-db 1.0.30001814
• 405baf1 Update caniuse-db 1.0.30001813
• See full diff in compare view

Updates electron-to-chromium from 1.5.439 to 1.5.444

Commits

• d391884 1.5.444
• 202b47d generate new version
• d330a11 1.5.443
• 27fc1c4 generate new version
• 0fa8331 1.5.442
• 79611e6 generate new version
• 781c0b2 1.5.441
• b891b61 generate new version
• 934130a 1.5.440
• 85084e5 generate new version
• See full diff in compare view

Updates enhanced-resolve from 5.25.1 to 5.26.0

Release notes

Sourced from enhanced-resolve's releases.

v5.26.0

Minor Changes

• Add experimental support for Node.js package maps through a new packageMap option, which takes the path of the configuration file (or a file: URL) or an already-parsed packages object. When it is set, a bare specifier is resolved through the importing package's dependencies table and the target package's location is handed to the regular pipeline, instead of walking node_modules; relative and absolute requests and node: builtins are unaffected. Because several package entries may share one url, the package a request resolved into is exposed as packageId on the result and can be passed back in as context.packageId to resolve from that package unambiguously. Package maps are stability 1 (experimental) in Node.js, and this option tracks that specification and may change with it. (by @​alexander-akait in #667)

• Explain an exports/imports field whose conditions wrap subpaths, instead of failing with a message that points at the request. A field shaped like { "import": { ".": "./esm/index.js", "./*": "./esm/*.js" }, "require": "./build/bundle.js" } is not supported by Node.js: the subpaths inside a condition are read as condition names, so they match nothing, and every request into the package failed as "./foo" is not exported under the conditions [...] — which reads as though the package forgot to export ./foo. Such a failure now names the offending keys and shows the arrangement that works, with the subpaths at the top level and the conditions nested inside them. Resolution itself is unchanged: the diagnosis runs only on a request that has already failed, so nothing that resolves today starts failing, and a successful resolve does no extra work. Errors raised while processing either field also name the package.json they came from, which previously only appeared in the resolver log. (by @​alexander-akait in #676)

• Generate the published type declarations with TypeScript instead of webpack/tooling, which is no longer a dependency. Every name the package exported before is still exported, and types.d.ts is still the entry point, but the declarations themselves now live in types/ and are emitted by tsc from the JSDoc in lib/. Two shapes follow the sources more closely than the previous generator did: the object form of Plugin no longer declares this: Resolver on apply (it is called as plugin.apply(resolver), so this is the plugin), and the entries of ResolveContext.stack declare name: string | undefined rather than an optional name. Class fields that the old generator dropped, such as the cache backends on CachedInputFileSystem, are now part of the declarations. (by @​alexander-akait in #675)

Patch Changes

• Size the ancestor path and segment arrays that getPathsCached keeps to what they actually hold: a push-built store keeps room for 17 entries while a path has a handful, and the cache holds these for the filesystem's lifetime. (by @​alexander-akait in #681)

Changelog

Sourced from enhanced-resolve's changelog.

5.26.0

Minor Changes

• Add experimental support for Node.js package maps through a new packageMap option, which takes the path of the configuration file (or a file: URL) or an already-parsed packages object. When it is set, a bare specifier is resolved through the importing package's dependencies table and the target package's location is handed to the regular pipeline, instead of walking node_modules; relative and absolute requests and node: builtins are unaffected. Because several package entries may share one url, the package a request resolved into is exposed as packageId on the result and can be passed back in as context.packageId to resolve from that package unambiguously. Package maps are stability 1 (experimental) in Node.js, and this option tracks that specification and may change with it. (by @​alexander-akait in #667)

• Explain an exports/imports field whose conditions wrap subpaths, instead of failing with a message that points at the request. A field shaped like { "import": { ".": "./esm/index.js", "./*": "./esm/*.js" }, "require": "./build/bundle.js" } is not supported by Node.js: the subpaths inside a condition are read as condition names, so they match nothing, and every request into the package failed as "./foo" is not exported under the conditions [...] — which reads as though the package forgot to export ./foo. Such a failure now names the offending keys and shows the arrangement that works, with the subpaths at the top level and the conditions nested inside them. Resolution itself is unchanged: the diagnosis runs only on a request that has already failed, so nothing that resolves today starts failing, and a successful resolve does no extra work. Errors raised while processing either field also name the package.json they came from, which previously only appeared in the resolver log. (by @​alexander-akait in #676)

• Generate the published type declarations with TypeScript instead of webpack/tooling, which is no longer a dependency. Every name the package exported before is still exported, and types.d.ts is still the entry point, but the declarations themselves now live in types/ and are emitted by tsc from the JSDoc in lib/. Two shapes follow the sources more closely than the previous generator did: the object form of Plugin no longer declares this: Resolver on apply (it is called as plugin.apply(resolver), so this is the plugin), and the entries of ResolveContext.stack declare name: string | undefined rather than an optional name. Class fields that the old generator dropped, such as the cache backends on CachedInputFileSystem, are now part of the declarations. (by @​alexander-akait in #675)

Patch Changes

• Size the ancestor path and segment arrays that getPathsCached keeps to what they actually hold: a push-built store keeps room for 17 entries while a path has a handful, and the cache holds these for the filesystem's lifetime. (by @​alexander-akait in #681)

Commits

• c65e40a chore(release): new release (#674)
• 7ed8697 perf: size the paths a request walks from its split (#681)
• 7e37289 chore(deps-dev): bump the dependencies group with 4 updates (#680)
• cba4ba4 test(alias): cover compileAliasOptions bucketing and the onlyModule flag (#679)
• f07a030 feat: explain exports/imports conditions that wrap subpaths (#676)
• d9a13d7 chore(deps): bump codecov/codecov-action from 7.0.0 to 7.1.1 in the dependenc...
• f8d395e chore(deps-dev): bump the dependencies group with 6 updates (#677)
• e1bdb75 refactor: generate types with typescript instead of webpack/tooling (#675)
• 332d999 ci: cancel superseded pull request runs (#673)
• e638bc9 feat: experimental support for Node.js package maps (#667)
• See full diff in compare view

Updates memfs from 4.79.0 to 4.80.0

Release notes

Sourced from memfs's releases.

Release v4.80.0

What's Changed

• feat: allow configuring the synchronous FSA worker timeout by @​Firatakti in streamich/memfs#1298

New Contributors

• @​Firatakti made their first contribution in streamich/memfs#1298

Full Changelog: streamich/memfs@v4.79.0...v4.80.0

Commits

• adae41a chore: release v4.80.0
• d9cfa18 Merge pull request #1298 from Firatakti/codex/fsa-sync-timeout
• fe75fbc feat: allow configuring the synchronous FSA worker timeout
• See full diff in compare view

Updates @parcel/watcher from 2.5.1 to 2.6.0

Release notes

Sourced from @​parcel/watcher's releases.

v2.6.0

Adds support RegExp ignores in parcel-bundler/watcher#248. Thanks @​SimenB!

v2.5.6

What's Changed

• chore: add stack-protector-strong flag by @​rzhao271 in parcel-bundler/watcher#236
• fix windows ia32 build by @​bpasero in parcel-bundler/watcher#237
• v2.5.6 by @​bpasero in parcel-bundler/watcher#238

Full Changelog: parcel-bundler/watcher@v2.5.5...v2.5.6

v2.5.4

What's Changed

• patch: fix SEGV due to Static Initialization Order Fiasco bug by @​alichtman in parcel-bundler/watcher#208
• Resolve several BinSkim issues by @​rzhao271 in parcel-bundler/watcher#202
• upgrade detect-libc for better compatibility by @​nicksrandall in parcel-bundler/watcher#200
• Don't show error messages when checking if watchman is available by @​aptinio in parcel-bundler/watcher#198
• Add Meteor to list of users by @​harryadel in parcel-bundler/watcher#214
• Fix CI by @​tmm1 in parcel-bundler/watcher#213
• Fix more SIOF / SDOF issues by @​alichtman in parcel-bundler/watcher#216
• Resolve more BinSkim issues by @​rzhao271 in parcel-bundler/watcher#219
• Remove D_FORTIFY_SOURCE flag by @​bpasero in parcel-bundler/watcher#223
• Fix use of delete operators by @​matttyson in parcel-bundler/watcher#145
• Some minor fixes found doing code review by @​bpasero in parcel-bundler/watcher#222
• Reduce dependencies by switching to picomatch by @​benmccann in parcel-bundler/watcher#210
• Fix glob tests on windows by going back to picomatch@2.3.1 by @​bpasero in parcel-bundler/watcher#224
• v2.5.2 by @​bpasero in parcel-bundler/watcher#225
• eng - update actions versions by @​bpasero in parcel-bundler/watcher#226
• v2.5.3 by @​bpasero in parcel-bundler/watcher#227
• Test on current versions of Node.js by @​cclauss in parcel-bundler/watcher#221
• eng - try to fix release script to publish new NPM version by @​bpasero in parcel-bundler/watcher#228
• v2.5.4 by @​bpasero in parcel-bundler/watcher#229

New Contributors

• @​alichtman made their first contribution in parcel-bundler/watcher#208
• @​rzhao271 made their first contribution in parcel-bundler/watcher#202
• @​nicksrandall made their first contribution in parcel-bundler/watcher#200
• @​aptinio made their first contribution in parcel-bundler/watcher#198
• @​harryadel made their first contribution in parcel-bundler/watcher#214
• @​matttyson made their first contribution in parcel-bundler/watcher#145
• @​benmccann made their first contribution in parcel-bundler/watcher#210
• @​cclauss made their first contribution in parcel-bundler/watcher#221

Full Changelog: parcel-bundler/watcher@v2.5.1...v2.5.4

Commits

• 01c4add v2.6.0
• 2392f96 fix ci
• 2d44c97 update ci
• e0c2dec only test on node lts
• 66e8e76 fix: use assert.rejects for async subscribe throw test (#254)
• a1b86cf chore: run prettier (#249)
• 4aa3dca feat: support RegExp ignores (#248)
• 8926bb8 v2.5.6 (#238)
• 6af4420 fix windows ia32 build (#237)
• e05e724 chore: add stack-protector-strong flag (#236)
• Additional commits viewable in compare view

Updates detect-libc from 1.0.3 to 2.1.2

Changelog

Sourced from detect-libc's changelog.

2.1.2 (2025-10-05)

• Add semi-automated changelog #32 (a950b06), closes #32
• Ensure Node.js 10 and 12 can use async file-based detection methods (#33) (a418065), closes #33

2.1.1 (2025-09-24)

• Ensure Node.js 10 and 12 can use file-based detection methods (#30) (e64be76), closes #30

2.1.0 (2025-09-14)

• CI: Add non-Linux integration tests for completeness (f9b7639)
• Detect libc using the interpreter value from Node's ELF header (4d6eafe)
• CI: Publish tagged commits to npm (08198d2)
• CI: update integration test expectations (3a1f323)

2.0.4 (2025-04-22)

• TypeScript: Add types field to package.json (#28) (0362727), closes #28
• CI: Add Node.js 20/22, remove CentOS (EOL) (3ed5518)
• CI: remove Node.js 22 (c04d3f2)

2.0.3 (2024-03-19)

• Improve filesystem-based detection of glibc (#22) (2642d96), closes #22
• Improve getReport performance (#21) (5e1482d), closes #21
• CI: bump unit test actions (646230f)
• CI: Latest Void Linux provides glibc 2.39 (2def922)
• CI: Update integration test environments/expectations (e307a53)
• Tests: include missing coverage in summary (9117b83)
• chore: refactor by removing a couple variables (#20) (8cf409b), closes #20

2.0.2 (2023-07-18)

• Add credit for e8c0afd (a3f3efb)
• Add SPDX identifiers to all source code files (d4fd207)
• Attempt to use contents of /usr/bin/ldd file for greater performance (#19) (e8c0afd), closes #19
• Ensure SPDX in header, correct grammar (4140056)
• CI: Add tests for Node.js 20 (a077cda)
• Docs: clarify 'version numbers' refers to libc (and not this package) (d49b8d3)
• Test: (unit) add Node.js 18 (integration) add Fedora 38, Ubuntu 22.04 (6761837)

2.0.1 (2022-02-14)

• Add Void Linux to integration tests (cde9231)
• Ensure TypeScript defs are valid, fixes initializer error (#15) (e7c02a7), closes #15
• CI: Switch CentOS 8 (EOL) to Stream (2bd0e69)

2.0.0 (2022-01-19)

... (truncated)

Commits

• 98928b7 Release v2.1.2
• a418065 Ensure Node.js 10 and 12 can use async file-based detection methods (#33)
• a950b06 Add semi-automated changelog #32
• 81ba742 Release v2.1.1
• e64be76 Ensure Node.js 10 and 12 can use file-based detection methods (#30)
• f74b368 Release v2.1.0
• f9b7639 CI: Add non-Linux integration tests for completeness
• 41add95 Prerelease v2.1.0-rc.0
• 08198d2 CI: Publish tagged commits to npm
• 4d6eafe Detect libc using the interpreter value from Node's ELF header
• Additional commits viewable in compare view

Maintainer changes

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

Updates shell-quote from 1.10.0 to 1.12.0

Changelog

Sourced from shell-quote's changelog.

v1.12.0 - 2026-10-02

Fixed

• [New] parse: support here-documents (<<) [#31](https://github.com/ljharb/shell-quote/issues/31)

Commits

• [New] parse: support tab-stripping here-documents (<<-) dbfac37
• [New] parse: support output process substitution (>() 2053315
• [New] parse: support the case test-next terminator (;;&) 7d688b9
• [New] parse: support the case fall-through terminator (;&) f27010e
• [New] parse: support redirecting output despite noclobber (>|) b78d19c
• [New] parse: support opening a file for reading and writing (<>) 21cc333
• [New] parse: support redirecting stdout and stderr (&>) 6ad6cd2
• [New] parse: support appending stdout and stderr (&>>) 90cde9c
• [Dev Deps] update @ljharb/eslint-config 3a7b4ae

v1.11.0 - 2026-09-29

Fixed

• [Refactor] quote: drop a replace that can never match in the single-quote branch [#15](https://github.com/ljharb/shell-quote/issues/15)
• [New] parse: support bash ANSI-C quoting ($'...') [#32](https://github.com/ljharb/shell-quote/issues/32)

Commits

• [Fix] quote: reject line terminators in tokens after a comment 6002b2e
• [Fix] parse: preserve text after special shell parameters 81b08a5
• [Fix] parse: an escaped backslash does not escape the character after it d708019
• [Fix] quote: preserve ! in arguments that also contain ' ad39927
• [Fix] parse: treat $_name as a variable name, not $_ followed by text 28f88cd
• [Fix] quote: preserve emp...

  Description has been truncated

[openshift-merge-bot]

Pipeline controller notification

This PR uses the pipeline controller for second-stage tests. Selection and triggering follow the repository configuration.

Use /test ? to list jobs, /pipeline remaining to request missing second-stage tests, or /pipeline required to rerun the selected second-stage set.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml
• Review profile: CHILL
• Plan: Enterprise
• Run ID: c0281a21-3282-4206-81d3-7d24a3f07cd2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], rszwajko

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [rszwajko]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

Scheduling required tests:
/test e2e-tests

[rszwajko]

/ok-to-test

[openshift-ci]

@dependabot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.