Skip to content

build(deps): bump webpack from 5.103.0 to 5.105.0 in /Legacy/old-codebase-artifacts/arkivermj#335

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/Legacy/old-codebase-artifacts/arkivermj/webpack-5.105.0
Closed

build(deps): bump webpack from 5.103.0 to 5.105.0 in /Legacy/old-codebase-artifacts/arkivermj#335
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/Legacy/old-codebase-artifacts/arkivermj/webpack-5.105.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 6, 2026

Bumps webpack from 5.103.0 to 5.105.0.

Release notes

Sourced from webpack's releases.

v5.105.0

Minor Changes

  • Allow resolving worker module by export condition name when using new Worker() (by @​hai-x in #20353)

  • Detect conditional imports to avoid compile-time linking errors for non-existent exports. (by @​hai-x in #20320)

  • Added the tsconfig option for the resolver options (replacement for tsconfig-paths-webpack-plugin). Can be false (disabled), true (use the default tsconfig.json file to search for it), a string path to tsconfig.json, or an object with configFile and references options. (by @​alexander-akait in #20400)

  • Support import.defer() for context modules. (by @​ahabhgk in #20399)

  • Added support for array values ​​to the devtool option. (by @​hai-x in #20191)

  • Improve rendering node built-in modules for ECMA module output. (by @​hai-x in #20255)

  • Unknown import.meta properties are now determined at runtime instead of being statically analyzed at compile time. (by @​xiaoxiaojx in #20312)

Patch Changes

  • Fixed ESM default export handling for .mjs files in Module Federation (by @​y-okt in #20189)

  • Optimized import.meta.env handling in destructuring assignments by using cached stringified environment definitions. (by @​xiaoxiaojx in #20313)

  • Respect the stats.errorStack option in stats output. (by @​samarthsinh2660 in #20258)

  • Fixed a bug where declaring a module variable in module scope would conflict with the default moduleArgument. (by @​xiaoxiaojx in #20265)

  • Fix VirtualUrlPlugin to set resourceData.context for proper module resolution. Previously, when context was not set, it would fallback to the virtual scheme path (e.g., virtual:routes), which is not a valid filesystem path, causing subsequent resolve operations to fail. (by @​xiaoxiaojx in #20390)

  • Fixed Worker self-import handling to support various URL patterns (e.g., import.meta.url, new URL(import.meta.url), new URL(import.meta.url, import.meta.url), new URL("./index.js", import.meta.url)). Workers that resolve to the same module are now properly deduplicated, regardless of the URL syntax used. (by @​xiaoxiaojx in #20381)

  • Reuse the same async entrypoint for the same Worker URL within a module to avoid circular dependency warnings when multiple Workers reference the same resource. (by @​xiaoxiaojx in #20345)

  • Fixed a bug where a self-referencing dependency would have an unused export name when imported inside a web worker. (by @​samarthsinh2660 in #20251)

  • Fix missing export generation when concatenated modules in different chunks share the same runtime in module library bundles. (by @​hai-x in #20346)

  • Fixed import.meta.env.xxx behavior: when accessing a non-existent property, it now returns empty object instead of full object at runtime. (by @​xiaoxiaojx in #20289)

  • Improved parsing error reporting by adding a link to the loader documentation. (by @​gaurav10gg in #20244)

  • Fix typescript types. (by @​alexander-akait in #20305)

  • Add declaration for unused harmony import specifier. (by @​hai-x in #20286)

  • Fix compressibility of modules while retaining portability. (by @​dmichon-msft in #20287)

  • Optimize source map generation: only include ignoreList property when it has content, avoiding empty arrays in source maps. (by @​xiaoxiaojx in #20319)

  • Preserve star exports for dependencies in ECMA module output. (by @​hai-x in #20293)

... (truncated)

Changelog

Sourced from webpack's changelog.

5.105.0

Minor Changes

  • Allow resolving worker module by export condition name when using new Worker() (by @​hai-x in #20353)

  • Detect conditional imports to avoid compile-time linking errors for non-existent exports. (by @​hai-x in #20320)

  • Added the tsconfig option for the resolver options (replacement for tsconfig-paths-webpack-plugin). Can be false (disabled), true (use the default tsconfig.json file to search for it), a string path to tsconfig.json, or an object with configFile and references options. (by @​alexander-akait in #20400)

  • Support import.defer() for context modules. (by @​ahabhgk in #20399)

  • Added support for array values ​​to the devtool option. (by @​hai-x in #20191)

  • Improve rendering node built-in modules for ECMA module output. (by @​hai-x in #20255)

  • Unknown import.meta properties are now determined at runtime instead of being statically analyzed at compile time. (by @​xiaoxiaojx in #20312)

Patch Changes

  • Fixed ESM default export handling for .mjs files in Module Federation (by @​y-okt in #20189)

  • Optimized import.meta.env handling in destructuring assignments by using cached stringified environment definitions. (by @​xiaoxiaojx in #20313)

  • Respect the stats.errorStack option in stats output. (by @​samarthsinh2660 in #20258)

  • Fixed a bug where declaring a module variable in module scope would conflict with the default moduleArgument. (by @​xiaoxiaojx in #20265)

  • Fix VirtualUrlPlugin to set resourceData.context for proper module resolution. Previously, when context was not set, it would fallback to the virtual scheme path (e.g., virtual:routes), which is not a valid filesystem path, causing subsequent resolve operations to fail. (by @​xiaoxiaojx in #20390)

  • Fixed Worker self-import handling to support various URL patterns (e.g., import.meta.url, new URL(import.meta.url), new URL(import.meta.url, import.meta.url), new URL("./index.js", import.meta.url)). Workers that resolve to the same module are now properly deduplicated, regardless of the URL syntax used. (by @​xiaoxiaojx in #20381)

  • Reuse the same async entrypoint for the same Worker URL within a module to avoid circular dependency warnings when multiple Workers reference the same resource. (by @​xiaoxiaojx in #20345)

  • Fixed a bug where a self-referencing dependency would have an unused export name when imported inside a web worker. (by @​samarthsinh2660 in #20251)

  • Fix missing export generation when concatenated modules in different chunks share the same runtime in module library bundles. (by @​hai-x in #20346)

  • Fixed import.meta.env.xxx behavior: when accessing a non-existent property, it now returns empty object instead of full object at runtime. (by @​xiaoxiaojx in #20289)

  • Improved parsing error reporting by adding a link to the loader documentation. (by @​gaurav10gg in #20244)

  • Fix typescript types. (by @​alexander-akait in #20305)

  • Add declaration for unused harmony import specifier. (by @​hai-x in #20286)

  • Fix compressibility of modules while retaining portability. (by @​dmichon-msft in #20287)

  • Optimize source map generation: only include ignoreList property when it has content, avoiding empty arrays in source maps. (by @​xiaoxiaojx in #20319)

... (truncated)

Commits
  • 1486f9a chore(release): new release
  • 1a517f6 feat: added the tsconfig option for the resolver options (#20400)
  • 7b3b0f7 feat: support import.defer() for context modules
  • c4a6a92 refactor: more types and increase types coverage
  • 5ecc58d feat: consider asset module as side-effect-free (#20352)
  • cce0f69 test: avoid comma operator in BinaryMiddleware test (#20398)
  • cd4793d feat: support import specifier guard (#20320)
  • fe48655 docs: update examples (#20397)
  • de107f8 fix(VirtualUrlPlugin): set resourceData.context to avoid invalid fallback (#2...
  • a656ab1 test: add self-import test case for dynamic import (#20389)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for webpack since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [webpack](https://github.com/webpack/webpack) from 5.103.0 to 5.105.0.
- [Release notes](https://github.com/webpack/webpack/releases)
- [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md)
- [Commits](webpack/webpack@v5.103.0...v5.105.0)

---
updated-dependencies:
- dependency-name: webpack
  dependency-version: 5.105.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Feb 6, 2026
@dependabot dependabot bot requested a review from MightyPrytanis as a code owner February 6, 2026 19:05
@MightyPrytanis MightyPrytanis self-assigned this Feb 8, 2026
MightyPrytanis added a commit that referenced this pull request Feb 21, 2026
…ies (#372)

Fixes Dependabot scanning legacy/archived code by adding `exclude-paths`
configuration to prevent dependency update PRs in frozen directories.

## Problem

PR #335 showed that Dependabot was creating PRs for dependencies in
`/Legacy/old-codebase-artifacts/arkivermj/`, proving that simply listing
explicit directories was insufficient. Dependabot scans ALL directories
in the repository by default, not just the ones listed in `directory`
fields.

## Changes

**`.github/dependabot.yml`** - Added functional `exclude-paths`
configuration:

- **exclude-paths added** - All 7 update entries now include:
  ```yaml
  exclude-paths:
    - "Legacy/**"
    - "archive/**"
  ```
- **Updated documentation** - Header now explains the use of
`exclude-paths` feature
- **Active directories** - Lists 7 scanned paths (`/Cyrano`,
`/apps/lexfiat`, `/apps/arkiver`, etc.)
- **Excluded paths** - `Legacy/**` and `archive/**` patterns block all
legacy code

## Technical Details

This uses GitHub's `exclude-paths` feature (added August 2025) to
actually prevent Dependabot from scanning manifest files in specified
paths. Unlike the `ignore` directive (which ignores specific
dependencies), `exclude-paths` prevents scanning entire directory trees.

This will prevent future PRs like #335 from being created for
archived/frozen code.

```yaml
# Dependabot configuration for Cyrano ecosystem
# Uses exclude-paths to prevent scanning /Legacy/ and /archive/ directories
#
# Active directories (scanned for dependency updates):
#   - /Cyrano (MCP server and core modules)
#   - /Cyrano/auth-server (authentication service)
#   ...
#
# Excluded paths (NOT scanned, frozen):
#   - Legacy/** (all archived legacy code)
#   - archive/** (all archive directories)
```

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> ## Problem Statement
> 
> We need to prevent Dependabot from updating dependencies in
archived/legacy code that should remain frozen. This includes:
> 
> 1. **Legacy directories in the monorepo** - Any directories under
`/Legacy/` or `/archive/` paths should not receive dependency updates
> 2. **Standalone repositories** - The following standalone repos should
have Dependabot disabled entirely:
>    - MightyPrytanis/SwimMeet
>    - MightyPrytanis/LexFiat  
>    - MightyPrytanis/Cyrano
>    - MightyPrytanis/Annunciator
> 
> ## Required Changes
> 
> ### For MightyPrytanis/codebase repository:
> 
> Update `.github/dependabot.yml` to add `ignore` conditions to each
package ecosystem configuration. Add the following ignore block to each
update entry:
> 
> ```yaml
> ignore:
>   # Ignore all dependencies in legacy/archive paths
>   - dependency-name: "*"
> update-types: ["version-update:semver-major",
"version-update:semver-minor", "version-update:semver-patch"]
> ```
> 
> However, note that Dependabot's `ignore` configuration only ignores
specific dependencies, not paths. Since the current configuration
already uses explicit directory targeting (only `/Cyrano`,
`/apps/lexfiat`, `/apps/arkiver`, etc.), and does NOT include `/Legacy/`
paths, these are already effectively excluded.
> 
> The more important issue is that there's a `/Legacy/SwimMeet/`
directory in the monorepo that should be explicitly documented as
excluded.
> 
> Update the comment at the top to clarify:
> ```yaml
> # Dependabot configuration for Cyrano ecosystem
> # Scans only active development directories
> # Explicitly excludes: /Legacy/, /archive/, and any archived code
> ```
> 
> ### For standalone repositories:
> 
> Create `.github/dependabot.yml` files (if they exist) in each
standalone repo and set them to disabled, OR delete existing
dependabot.yml files to disable Dependabot entirely.
> 
> For each of these repos:
> - MightyPrytanis/SwimMeet
> - MightyPrytanis/LexFiat
> - MightyPrytanis/Cyrano  
> - MightyPrytanis/Annunciator
> 
> **Note:** Based on the checks, these repos either don't have
Dependabot configurations or are not accessible. Since this PR is for
the `codebase` monorepo, focus on documenting that the legacy code in
`/Legacy/` is excluded.
> 
> ### Final Solution for codebase repo:
> 
> Update `.github/dependabot.yml` to:
> 1. Improve the header comment to explicitly state what's excluded
> 2. Keep the existing explicit directory configuration (which already
excludes Legacy)
> 3. Optionally add a comment section listing explicitly excluded
directories for documentation
> 
> The current configuration is already correct in that it only targets
active directories, but the documentation should be clearer.


</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

*This pull request was created from Copilot chat.*
>

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for
you](https://github.com/MightyPrytanis/codebase/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 21, 2026

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/Legacy/old-codebase-artifacts/arkivermj/webpack-5.105.0 branch February 21, 2026 22:02
@MightyPrytanis
Copy link
Owner

MightyPrytanis commented Feb 21, 2026

@dependabot it isn't that this release isn't valuable; its that the directory you targeted is legacy/archive and meant to be static–it's. no longer active or being updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant