Skip to content

chore(release): new release - #2393

Merged
bjohansebas merged 1 commit into
mainfrom
changeset-release/main
Sep 3, 2026
Merged

chore(release): new release#2393
bjohansebas merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

webpack-dev-middleware@8.3.0

Minor Changes

  • Added a hot option that enables hot module replacement, replacing the need for webpack-hot-middleware. Pass hot: true to enable with defaults, or hot: { path, heartbeat, progress, statsOptions } to customize. The client runtime is served by the middleware itself. (by @bjohansebas in #2370)

  • Take the diagnostics a hot payload carries from the stats option, so one setting governs what a build reports in the terminal and in the browser: stats: "errors-only" keeps warnings out of both, and stats: false keeps errors and warnings out of both, the client's error overlay included — reach for the client's ?logging= or ?overlay= to quiet the browser alone. hot.statsOptions is deprecated and will be removed in the next major release; its hash, timings and children keys are now ignored, because they could leave a payload without the hash the client compares, or carry a child compilation's hash instead, which stopped updates applying and forced a full page reload on every rebuild. (by @alexander-akait in #2392)

Patch Changes

  • Fixed a crash when calling invalidate() in plugin mode (isPlugin = true). Since the host (webpack-cli, webpack-dev-server, etc.) owns compiler.watch(), the middleware now invalidates the host's watching instead (each child compiler's one for a MultiCompiler on webpack < 5.109). When nothing is watching it logs a warning and completes the callback, as close() does, rather than leaving invalidate(callback) waiting on a build that never runs. (by @bjohansebas in #2378)

  • Reject with 403 Forbidden the requests whose resolved filename falls outside outputPath (GHSA-g84c-rxfj-3j2c). With a publicPath without a trailing slash, a sibling path sharing its prefix (/assets../secret) escaped the output root once the prefix was stripped and joined. (by @bjohansebas in #2404)

  • Update the changelog generator to the @changesets/get-github-info 1.0 API. (by @alexander-akait in #2396)

  • Update dependencies. (by @alexander-akait in #2394)

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 6 times, most recently from fcdf103 to c57f179 Compare September 2, 2026 17:31
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c57f179 to fd2ae8b Compare September 2, 2026 19:14
alexander-akait added a commit that referenced this pull request Sep 2, 2026
A pull request opened with the repository's own GITHUB_TOKEN does not
trigger workflows, so the release pull request never ran lint, the test
matrix or the client job -- #2393 has only the two Socket checks on it,
and with no checks reported it cannot be merged.

The repository already generates an app token for the dependabot
auto-merge workflow; the release job now does the same and hands it to
changesets/action. v2 takes a custom token through the github-token
input rather than the environment variable, which stays set because
changeset version runs the changelog generator against the GitHub API.
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from fd2ae8b to af122f3 Compare September 3, 2026 02:05
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from af122f3 to 8450cca Compare September 3, 2026 02:38
@bjohansebas
bjohansebas merged commit 1abbf08 into main Sep 3, 2026
3 checks passed
@bjohansebas
bjohansebas deleted the changeset-release/main branch September 3, 2026 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant