Bump the all group with 5 updates by dependabot[bot] · Pull Request #373 · spatial-model-editor/spatial-model-editor.github.io

dependabot · 2026-06-03T11:18:12Z

Bumps the all group with 5 updates:

Package	From	To
@11ty/eleventy	`3.1.5`	`3.1.6`
concurrently	`9.2.1`	`10.0.3`
webpack	`5.106.2`	`5.107.2`
webpack-cli	`7.0.2`	`7.0.3`
yaml	`2.8.3`	`2.9.0`

Updates @11ty/eleventy from 3.1.5 to 3.1.6

Release notes

Sourced from @11ty/eleventy's releases.

Eleventy v3.1.6: Everybody wants to do Maintenance

Fixes Node 26 module.register deprecation warning shown in console #4283 (fixed in v4 alphas in #4271)

Minor dependency upgrades for npm audit fixes

liquidjs upgrade from 1.25.0 to 1.27.0

markdown-it upgrade from 14.1.1 to 14.2.0

Adds Node 26 to CI for v3 branch

Opt out of package manager cache for GitHub Actions CI release workflow (hardening security)

Milestone: https://github.com/11ty/eleventy/milestone/52?closed=1 Full Changelog: 11ty/eleventy@v3.1.5...v3.1.6

Commits

02ad90a v3.1.6 and upgrade deps
3dc0566 Update release workflow for improved security
1b928f5 Adds Node 26 to CI for v3
0a3a4f4 Fixes #4283 (v3 branch only)
a7af61b Upgrade dependencies for audit fixes.
See full diff in compare view

Updates concurrently from 9.2.1 to 10.0.3

Release notes

Sourced from concurrently's releases.

v10.0.3

Republish of https://github.com/open-cli-tools/concurrently/releases/tag/v10.0.1 with Trusted Publishing enabled (see #595)

Full Changelog: open-cli-tools/concurrently@v10.0.2...v10.0.3

v10.0.2

Test version to restore Trusted Publishing. Not published to npm.

v10.0.1

Ensure FlowController type is exported - #594

Full Changelog: open-cli-tools/concurrently@v10.0.0...v10.0.1

v10.0.0

💥 Breaking Changes

Dropped support for Node.js <22.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

concurrently is now ESM-only. It's now possible to require(esm). See here for interoperability.

Prefix colors now default to automatic - #581 The colors used to default to reset (which does nothing). Concurrently now automatically selects a color, out of the box. The list of colors used is not jarring nor carries semantic meaning, and reads well in both dark and light terminal backgrounds.

Removed deprecated flags and options

CLI flag --name-separator: use commas instead.

API option killOthers: use killOthersOn instead.

✨ New Features

Support applying modifiers to hex prefix colors (e.g. #ff0000.bold) - #450

Support chalk's color functions in prefixes (e.g. rgb(), hex(), bgRgb(), etc) - #578

Set prefix background color via bg#RRGGBB - #578

Allow shell override via --shell CLI flag/shell API option - #288, #589, #556 concurrently distinguishes between cmd.exe, powershell, and POSIX-based shells.

Manual prefix coloring in templates e.g. [{color}{name}{/color}] - #583, #587

🐛 Bug fixes

Scope quote normalization to CLI input - #582, #585 It should now also be possible to run commands like "/some/command" foo bar"

Don't throw when color doesn't exist - #580

🔐 Security

Address vulnerability in shellquote - #591

Other changes

Warn about running on Snap - #584

New Contributors

@philfreo made their first contribution in open-cli-tools/concurrently#566

@garretmh made their first contribution in open-cli-tools/concurrently#450

@CodeF53 made their first contribution in open-cli-tools/concurrently#574

@nkappler made their first contribution in open-cli-tools/concurrently#577

... (truncated)

Commits

435f61b 10.0.3
5ea69c6 ci: use node 24 in the release workflow
18e1281 10.0.2
e70686f 10.0.1
a95bceb Rename flow-controller{.d -> }.ts
ced4245 ci: configure trusted publisher flow
cf2eaa2 10.0.0
1b9bae4 deps: upgrade yargs to v18 (#593)
b05ee75 Bump min Node.js version to v22
ae60bc4 Scope quote normalization to CLI input (#585)
Additional commits viewable in compare view

Maintainer changes

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

Updates webpack from 5.106.2 to 5.107.2

Release notes

Sourced from webpack's releases.

v5.107.2

Patch Changes

Reduce per-file overhead in ContextModuleFactory.resolveDependencies by batching alternativeRequests hook calls. Previously the hook was invoked once per file in the context (with a single-item array), paying per-call overhead (closure allocation, resolverFactory.get, intermediate arrays in RequireContextPlugin) for every file. The hook is now invoked once per directory with all matched files in one batch — RequireContextPlugin's tap already iterates the items array, so the output is unchanged. Steady-state rebuild on a 4000-file require.context drops a further ~15 ms (after the watch-mode purge fix in the same release). (by @alexander-akait in #21020)

Include each external info's runtimeCondition in ConcatenatedModule#updateHash so changes to a concatenated external's runtime condition invalidate persistent caches instead of slipping through with the module id alone. (by @alexander-akait in #21023)

Fix HTML [contenthash] for referenced asset and inline-style URL changes. (by @alexander-akait in #21018)

Resolve chunk-hash placeholders in chunk URLs embedded into extracted HTML. (by @alexander-akait in #21018)

Remove unnecessary __webpack_require__ runtime helpers in ESM library output with multi-module chunks. (by @xiaoxiaojx in #21032)

Rewrite NormalModule#getSideEffectsConnectionState walk as an allocation-light iterative loop instead of a generator trampoline, restoring rebuild performance lost in #20993 while keeping deep import chains stack-safe. (by @alexander-akait in #21014)

Fix runtime ReferenceError on the first activation of a lazy-compiled module when output.library.type produces a closure-wrapped bundle (umd, umd2, amd, amd-require, system). (by @alexander-akait in #21013)

External modules of these types reference closure-bound identifiers like __WEBPACK_EXTERNAL_MODULE_react__, supplied by the library wrapper that is generated once per chunk. When lazyCompilation activates an entry or import for the first time, any external dependency the lazily-built module pulls in arrives in a hot-update chunk that lives outside the original wrapper closure, so its factory body cannot resolve the closure identifier and only a manual page refresh recovers.

The inactive LazyCompilationProxyModule now declares statically-enumerable externals (string and object forms of externals) as its own dependencies, so the initial entry chunk's library wrapper already exposes their closure identifiers. When activation later pulls in those externals through the lazily-compiled module, they resolve to the already-installed factories instead of throwing. Function and RegExp externals are not pre-populated because their effective request set isn't knowable up front.

Fill in missing entryOptions when an async block joins an existing entrypoint. (by @alexander-akait in #21026)

Release per-child codeGenerationResults in MultiCompiler and at Compiler.close to reduce memory retention. (by @alexander-akait in #21015)

Reduce peak memory of SourceMapDevToolPlugin on large builds (closes #20961). (by @alexander-akait in #20963)

Fix slow require.context() / dynamic import() rebuilds in watch mode (#13636). When a file inside a watched context directory changed, NodeWatchFileSystem would call inputFileSystem.purge(contextDir). The enhanced-resolve purge implementation matches cache keys with key.startsWith(contextDir), so the stat cache of every file under the directory was discarded on every rebuild — ContextModuleFactory.resolveDependencies then re-stat-ed the whole tree on each rebuild. Single-file rebuilds on a 4000-file context now reuse the warm stat cache, dropping median rebuild from ~1260 ms to ~650 ms in a local reproduction (≈49%). For directory items that are explicitly watched contexts, purge is now called with { exact: true } (added in enhanced-resolve@5.22.0) so only the directory's own entry is invalidated; file-level changes in the same aggregated event continue to purge file stats and the parent readdir as before. (by @alexander-akait in #21020)

v5.107.1

Patch Changes

Align the experimental HTML tokenizer with the WHATWG spec: fix offset-range bugs in the script-data, content-mode end-tag, attribute-value, and EOF states; surface tokenizer parse errors to consumers via a new parseError callback ("warning" when the tokenizer recovers and the emitted token is still well-formed, "error" when the offset range is incomplete — e.g. eof-in-tag); and add the full WHATWG named character references table so decodeHtmlEntities handles all named entities (including legacy bare forms like &AMP and multi-code-point entities like &NotEqualTilde;) with proper longest-prefix backtracking. (by @alexander-akait in #21000)

Tree-shake CommonJS modules imported through a const NAME = require(LITERAL) binding when only static members of NAME are read. Previously webpack treated every export of such modules as referenced (because the bare require() dependency reports EXPORTS_OBJECT_REFERENCED), so unused exports.x = ... assignments remained in the bundle even with usedExports enabled. The parser now forwards NAME.x / NAME.x() / NAME["x"] accesses to the underlying CommonJsRequireDependency as referenced exports, falling back to the full exports object the moment NAME is read in any other context (passed by value, destructured later, accessed with a dynamic key, …). This brings the binding form to parity with the existing destructuring form (const { x } = require(...)). (by @alexander-akait in #21003)

Fix RangeError: Maximum call stack size exceeded thrown from HarmonyImportSideEffectDependency.getModuleEvaluationSideEffectsState on long linear chains of side-effect-free imports. NormalModule.getSideEffectsConnectionState previously descended through HarmonyImportSideEffectDependency.getModuleEvaluationSideEffectsState recursively, adding two stack frames per module, which overflowed V8's stack at a few thousand modules deep. The traversal is now iterative. (by @alexander-akait in #20993)

Fix NormalModuleFactory parser/generator types: (by @alexander-akait in #20999)

module.generator.html now uses HtmlGeneratorOptions instead of EmptyGeneratorOptions (the extract option was hidden from the createGenerator / generator hook types).

WebAssembly (webassembly/async, webassembly/sync) generator hooks now use EmptyGeneratorOptions instead of EmptyParserOptions.

NormalModuleFactory#getParser / createParser / getGenerator / createGenerator are now generic over the module-type string, returning the specific parser/generator class for known types (e.g. JavascriptParser for "javascript/auto", CssGenerator for "css", etc.) instead of always returning the base Parser / Generator.

NormalModuleCreateData is now generic over the module type so parser, parserOptions, generator, and generatorOptions are narrowed to the specific class / options for the given type.

Link import bindings used inside define(...) callbacks in ES modules. Previously, HarmonyDetectionParserPlugin skipped walking the arguments of define calls in harmony modules, so references to imported bindings inside an inline AMD define factory (e.g. define(function () { console.log(foo); })) were not rewritten to their imported references and could cause ReferenceError at runtime. Inner graph usage analysis is also fixed for the related pattern const fn = function () { foo; }; define(fn);. (by @alexander-akait in #20990)

HTML-entry pipeline (experiments.html + experiments.css): emit <link rel="stylesheet"> tags for CSS chunks reachable from a <script src> entry. Previously when the bundled JS imported CSS, the resulting .css file was emitted to disk but never referenced from the extracted HTML (no <link> tag), and when splitChunks extracted CSS into sibling chunks the HTML cloned the originating <script> for each one — producing <script src="style.js"> pointing at non-existent JS filenames instead of <link rel="stylesheet" href="style.css">. CSS chunks are now sorted by the entrypoint's module post-order index so the <link> tags also appear in source import order, fixing the cascade ordering issue documented in html-webpack-plugin#1838 and webpack/mini-css-extract-plugin#959 for HTML-entry builds. nonce/crossorigin/referrerpolicy are copied from the originating tag onto the emitted <link>. (by @alexander-akait in #21002)

Allow devtool and SourceMapDevToolPlugin (or multiple SourceMapDevToolPlugin instances) to coexist on the same asset. Previously the second instance would silently skip any asset whose info.related.sourceMap had already been set by an earlier instance, and even when it ran the asset had been rewrapped as a RawSource so no source map could be recovered — producing an empty .map file. The plugin now keeps a per-compilation stash of pristine source maps, namespaces its persistent cache entries by the options that affect output, and appends additional related.sourceMap entries instead of overwriting them. The classic workaround of pairing devtool: 'hidden-source-map' with a new webpack.SourceMapDevToolPlugin({ filename: '[file].secondary.map', noSources: true }) now produces both maps in a single build. (by @alexander-akait in #21001)

... (truncated)

Changelog

Sourced from webpack's changelog.

5.107.2

Patch Changes

Reduce per-file overhead in ContextModuleFactory.resolveDependencies by batching alternativeRequests hook calls. Previously the hook was invoked once per file in the context (with a single-item array), paying per-call overhead (closure allocation, resolverFactory.get, intermediate arrays in RequireContextPlugin) for every file. The hook is now invoked once per directory with all matched files in one batch — RequireContextPlugin's tap already iterates the items array, so the output is unchanged. Steady-state rebuild on a 4000-file require.context drops a further ~15 ms (after the watch-mode purge fix in the same release). (by @alexander-akait in #21020)

Include each external info's runtimeCondition in ConcatenatedModule#updateHash so changes to a concatenated external's runtime condition invalidate persistent caches instead of slipping through with the module id alone. (by @alexander-akait in #21023)

Fix HTML [contenthash] for referenced asset and inline-style URL changes. (by @alexander-akait in #21018)

Resolve chunk-hash placeholders in chunk URLs embedded into extracted HTML. (by @alexander-akait in #21018)

Remove unnecessary __webpack_require__ runtime helpers in ESM library output with multi-module chunks. (by @xiaoxiaojx in #21032)

Rewrite NormalModule#getSideEffectsConnectionState walk as an allocation-light iterative loop instead of a generator trampoline, restoring rebuild performance lost in #20993 while keeping deep import chains stack-safe. (by @alexander-akait in #21014)

Fix runtime ReferenceError on the first activation of a lazy-compiled module when output.library.type produces a closure-wrapped bundle (umd, umd2, amd, amd-require, system). (by @alexander-akait in #21013)

External modules of these types reference closure-bound identifiers like __WEBPACK_EXTERNAL_MODULE_react__, supplied by the library wrapper that is generated once per chunk. When lazyCompilation activates an entry or import for the first time, any external dependency the lazily-built module pulls in arrives in a hot-update chunk that lives outside the original wrapper closure, so its factory body cannot resolve the closure identifier and only a manual page refresh recovers.

The inactive LazyCompilationProxyModule now declares statically-enumerable externals (string and object forms of externals) as its own dependencies, so the initial entry chunk's library wrapper already exposes their closure identifiers. When activation later pulls in those externals through the lazily-compiled module, they resolve to the already-installed factories instead of throwing. Function and RegExp externals are not pre-populated because their effective request set isn't knowable up front.

Fill in missing entryOptions when an async block joins an existing entrypoint. (by @alexander-akait in #21026)

Release per-child codeGenerationResults in MultiCompiler and at Compiler.close to reduce memory retention. (by @alexander-akait in #21015)

Reduce peak memory of SourceMapDevToolPlugin on large builds (closes #20961). (by @alexander-akait in #20963)

Fix slow require.context() / dynamic import() rebuilds in watch mode (#13636). When a file inside a watched context directory changed, NodeWatchFileSystem would call inputFileSystem.purge(contextDir). The enhanced-resolve purge implementation matches cache keys with key.startsWith(contextDir), so the stat cache of every file under the directory was discarded on every rebuild — ContextModuleFactory.resolveDependencies then re-stat-ed the whole tree on each rebuild. Single-file rebuilds on a 4000-file context now reuse the warm stat cache, dropping median rebuild from ~1260 ms to ~650 ms in a local reproduction (≈49%). For directory items that are explicitly watched contexts, purge is now called with { exact: true } (added in enhanced-resolve@5.22.0) so only the directory's own entry is invalidated; file-level changes in the same aggregated event continue to purge file stats and the parent readdir as before. (by @alexander-akait in #21020)

5.107.1

Patch Changes

Align the experimental HTML tokenizer with the WHATWG spec: fix offset-range bugs in the script-data, content-mode end-tag, attribute-value, and EOF states; surface tokenizer parse errors to consumers via a new parseError callback ("warning" when the tokenizer recovers and the emitted token is still well-formed, "error" when the offset range is incomplete — e.g. eof-in-tag); and add the full WHATWG named character references table so decodeHtmlEntities handles all named entities (including legacy bare forms like &AMP and multi-code-point entities like &NotEqualTilde;) with proper longest-prefix backtracking. (by @alexander-akait in #21000)

Tree-shake CommonJS modules imported through a const NAME = require(LITERAL) binding when only static members of NAME are read. Previously webpack treated every export of such modules as referenced (because the bare require() dependency reports EXPORTS_OBJECT_REFERENCED), so unused exports.x = ... assignments remained in the bundle even with usedExports enabled. The parser now forwards NAME.x / NAME.x() / NAME["x"] accesses to the underlying CommonJsRequireDependency as referenced exports, falling back to the full exports object the moment NAME is read in any other context (passed by value, destructured later, accessed with a dynamic key, …). This brings the binding form to parity with the existing destructuring form (const { x } = require(...)). (by @alexander-akait in #21003)

Fix RangeError: Maximum call stack size exceeded thrown from HarmonyImportSideEffectDependency.getModuleEvaluationSideEffectsState on long linear chains of side-effect-free imports. NormalModule.getSideEffectsConnectionState previously descended through HarmonyImportSideEffectDependency.getModuleEvaluationSideEffectsState recursively, adding two stack frames per module, which overflowed V8's stack at a few thousand modules deep. The traversal is now iterative. (by @alexander-akait in #20993)

Fix NormalModuleFactory parser/generator types: (by @alexander-akait in #20999)

module.generator.html now uses HtmlGeneratorOptions instead of EmptyGeneratorOptions (the extract option was hidden from the createGenerator / generator hook types).

WebAssembly (webassembly/async, webassembly/sync) generator hooks now use EmptyGeneratorOptions instead of EmptyParserOptions.

NormalModuleFactory#getParser / createParser / getGenerator / createGenerator are now generic over the module-type string, returning the specific parser/generator class for known types (e.g. JavascriptParser for "javascript/auto", CssGenerator for "css", etc.) instead of always returning the base Parser / Generator.

NormalModuleCreateData is now generic over the module type so parser, parserOptions, generator, and generatorOptions are narrowed to the specific class / options for the given type.

Link import bindings used inside define(...) callbacks in ES modules. Previously, HarmonyDetectionParserPlugin skipped walking the arguments of define calls in harmony modules, so references to imported bindings inside an inline AMD define factory (e.g. define(function () { console.log(foo); })) were not rewritten to their imported references and could cause ReferenceError at runtime. Inner graph usage analysis is also fixed for the related pattern const fn = function () { foo; }; define(fn);. (by @alexander-akait in #20990)

HTML-entry pipeline (experiments.html + experiments.css): emit <link rel="stylesheet"> tags for CSS chunks reachable from a <script src> entry. Previously when the bundled JS imported CSS, the resulting .css file was emitted to disk but never referenced from the extracted HTML (no <link> tag), and when splitChunks extracted CSS into sibling chunks the HTML cloned the originating <script> for each one — producing <script src="style.js"> pointing at non-existent JS filenames instead of <link rel="stylesheet" href="style.css">. CSS chunks are now sorted by the entrypoint's module post-order index so the <link> tags also appear in source import order, fixing the cascade ordering issue documented in html-webpack-plugin#1838 and webpack/mini-css-extract-plugin#959 for HTML-entry builds. nonce/crossorigin/referrerpolicy are copied from the originating tag onto the emitted <link>. (by @alexander-akait in #21002)

... (truncated)

Commits

cfb24a4 chore(release): new release (#21019)
c7d8a3a fix: release per-child Compilation heap pressure in MultiCompiler (#21015)
d6cdebe fix: regression in types for ProgressPlugin (#21036)
c073890 fix: gap-fill entryOptions when an async block reuses an existing entrypoint ...
78158f0 docs: streamline AGENTS.md to reduce AI hallucination (#21033)
c61c649 test: fail on missing per-kind snapshot instead of auto-writing it (#21027)
a514897 docs: update examples (#21031)
cc4035b fix: remove unnecessary webpack_require in ESM library output (#21032)
12cb825 docs(buildChunkGraph): explain why blocksWithNestedBlocks gates the skip (#21...
75f60f6 fix(ConcatenatedModule): include runtimeCondition of external infos in update...
Additional commits viewable in compare view

Updates webpack-cli from 7.0.2 to 7.0.3

Release notes

Sourced from webpack-cli's releases.

webpack-cli@7.0.3

Patch Changes

Improved CLI startup performance and reduced memory usage. (by @alexander-akait in #4765)

Reduced CLI startup CPU and memory usage by caching schema-derived argument metadata, registering only the options present in the arguments, and reading config directories once during default-config discovery. (by @alexander-akait in #4760)

Replace the fastest-levenshtein dependency with a small in-tree implementation used for command/option "did you mean" suggestions. (by @alexander-akait in #4762)

Changelog

Sourced from webpack-cli's changelog.

7.0.3

Patch Changes

Improved CLI startup performance and reduced memory usage. (by @alexander-akait in #4765)

Reduced CLI startup CPU and memory usage by caching schema-derived argument metadata, registering only the options present in the arguments, and reading config directories once during default-config discovery. (by @alexander-akait in #4760)

Replace the fastest-levenshtein dependency with a small in-tree implementation used for command/option "did you mean" suggestions. (by @alexander-akait in #4762)

Commits

5fb92f3 chore(release): new release (#4711)
00347ed perf(webpack-cli): allocate Levenshtein buffer lazily (#4765)
1b40b72 chore: update ejs (#4764)
2bbb639 refactor(webpack-cli): replace fastest-levenshtein with in-tree implementatio...
a467d6e chore(deps): bump the dependencies group across 1 directory with 10 updates (...
183d0e6 perf(webpack-cli): cache schema arguments and use map lookups for options (#4...
5b33f70 chore(deps-dev): bump sass-loader from 16.0.8 to 17.0.0 (#4756)
59f362a chore(deps): bump qs and express (#4758)
eaffa0b chore(deps): bump codecov/codecov-action in the dependencies group (#4757)
b3498b6 chore(deps): bump the dependencies group with 3 updates (#4754)
Additional commits viewable in compare view

Updates yaml from 2.8.3 to 2.9.0

Release notes

Sourced from yaml's releases.

v2.9.0

The changes here are really only patches, but I'm releasing this as a minor version to note a small change to the documentation of parseDocument() and parseAllDocuments(): I've removed the claim that they'll "never throw".

It remains the case that practically all non-malicious inputs will be handled without emitting an error, but there is a decent chance that code paths remain where e.g. a RangeError due to call stack exhaustion can be triggered by malicious inputs. Up to now, I've considered these as security vulnerabilities, and in fact it's the only category of error for which yaml CVEs have been issued so far.

Starting from this release, I'll be considering such errors as bugs, but not vulnerabilities. I do welcome people and/or LLMs looking for them, but please report them as normal issues rather than suspected security vulnerabilities. This also applies to previously undiscovered bugs in earlier releases.

fix: Avoid calling Array.prototype.push.apply() with large source array

fix(lexer): Avoid recursive calls that may exhaust the call stack

v2.8.4

Disable alias resolution with maxAliasCount:0 (#677)

Handle invalid unicode escapes (e1a1a77)

Apply minFractionDigits only to decimal strings (#676)

Commits

ddb21b0 2.9.0
167365b docs: Clarify that not all errors can be avoided
6eca2a7 fix: Avoid calling Array.prototype.push.apply() with large source array
0543cd5 fix(lexer): Avoid recursive calls that may exhaust the call stack
ccdf743 2.8.4
f625789 fix: Disable alias resolution with maxAliasCount:0 (#677)
e1a1a77 fix: Handle invalid unicode escapes
a163ea0 style: Satify Prettier
b2a5a6c fix: Apply minFractionDigits only to decimal strings (#676)
93c951b chore: Bump JSR version to v2.8.3 (#673)
Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the all group with 5 updates: | Package | From | To | | --- | --- | --- | | [@11ty/eleventy](https://github.com/11ty/eleventy) | `3.1.5` | `3.1.6` | | [concurrently](https://github.com/open-cli-tools/concurrently) | `9.2.1` | `10.0.3` | | [webpack](https://github.com/webpack/webpack) | `5.106.2` | `5.107.2` | | [webpack-cli](https://github.com/webpack/webpack-cli) | `7.0.2` | `7.0.3` | | [yaml](https://github.com/eemeli/yaml) | `2.8.3` | `2.9.0` | Updates `@11ty/eleventy` from 3.1.5 to 3.1.6 - [Release notes](https://github.com/11ty/eleventy/releases) - [Changelog](https://github.com/11ty/eleventy/blob/main/docs/release-instructions.md) - [Commits](11ty/eleventy@v3.1.5...v3.1.6) Updates `concurrently` from 9.2.1 to 10.0.3 - [Release notes](https://github.com/open-cli-tools/concurrently/releases) - [Commits](open-cli-tools/concurrently@v9.2.1...v10.0.3) Updates `webpack` from 5.106.2 to 5.107.2 - [Release notes](https://github.com/webpack/webpack/releases) - [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md) - [Commits](webpack/webpack@v5.106.2...v5.107.2) Updates `webpack-cli` from 7.0.2 to 7.0.3 - [Release notes](https://github.com/webpack/webpack-cli/releases) - [Changelog](https://github.com/webpack/webpack-cli/blob/main/CHANGELOG.md) - [Commits](https://github.com/webpack/webpack-cli/compare/webpack-cli@7.0.2...webpack-cli@7.0.3) Updates `yaml` from 2.8.3 to 2.9.0 - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.8.3...v2.9.0) --- updated-dependencies: - dependency-name: "@11ty/eleventy" dependency-version: 3.1.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: all - dependency-name: concurrently dependency-version: 10.0.3 dependency-type: direct:development update-type: version-update:semver-major dependency-group: all - dependency-name: webpack dependency-version: 5.107.2 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: all - dependency-name: webpack-cli dependency-version: 7.0.3 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: all - dependency-name: yaml dependency-version: 2.9.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: all ... Signed-off-by: dependabot[bot] <support@github.com>

for more information, see https://pre-commit.ci

dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 3, 2026

[pre-commit.ci] auto fixes from pre-commit.com hooks

928ccba

for more information, see https://pre-commit.ci

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump the all group with 5 updates#373

Bump the all group with 5 updates#373
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/all-cf5ff5a1e1

dependabot Bot commented on behalf of github Jun 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Jun 3, 2026

Eleventy v3.1.6: Everybody wants to do Maintenance

v10.0.3

v10.0.2

v10.0.1

v10.0.0

💥 Breaking Changes

✨ New Features

🐛 Bug fixes

🔐 Security

Other changes

New Contributors

v5.107.2

Patch Changes

v5.107.1

Patch Changes

5.107.2

Patch Changes

5.107.1

Patch Changes

webpack-cli@7.0.3

Patch Changes

7.0.3

Patch Changes

v2.9.0

v2.8.4

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants