chore(deps): bump vite from 6.4.3 to 8.2.1 in /examples/browser in the examples-npm group across 1 directory - #2313
Merged
chaliy merged 1 commit intoAug 19, 2026
Conversation
Bumps the examples-npm group with 1 update in the /examples/browser directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Updates `vite` from 6.4.3 to 8.2.1 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.2.1/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.2.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: examples-npm ... Signed-off-by: dependabot[bot] <support@github.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 7d8eb53 | Commit Preview URL Branch Preview URL |
Aug 19 2026, 09:29 AM |
chaliy
deleted the
dependabot/npm_and_yarn/examples/browser/examples-npm-7f7e8a2361
branch
August 19, 2026 09:57
2 tasks done
chaliy
added a commit
that referenced
this pull request
Aug 19, 2026
…n CI (#2316) examples/browser/dependency-security.test.js asserts every dependency is pinned to an exact version next to a committed lockfile - the reproducibility guard for the one example that loads a published npm package. Nothing in CI ran it. So it stopped holding without anyone noticing: vite sat on ^6.4.3, and dependabot (which preserves the range style it finds) carried the caret straight through a two-major bump to ^8.2.1 in #2313. A caret range plus a lockfile means a fresh install outside the lockfile resolves something nobody reviewed. Pin vite to 8.2.1 so the guard passes (9/9, was 8/9), and run the suite from the Examples job so it cannot silently rot again. It runs there rather than in js.yml deliberately: the suite is plain `node --test` with no install step - its fakes stand in for the wasm package, so it costs about a second - while js.yml builds the napi binding and filters on paths that exclude examples/browser, meaning the guard would not fire on the package.json edits it exists to catch. The step asserts the test files exist before running them, because `node --test` exits 0 when its argument matches nothing; without that a renamed suite would report green having run zero tests. Verified in CI: the step lists both files and reports 9 tests, 9 pass, 0 fail.
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the examples-npm group with 1 update in the /examples/browser directory: vite.
Updates
vitefrom 6.4.3 to 8.2.1Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
4216158release: v8.2.1fddf4eafix(server): use a random port when port is 0 (#23158)de041a7fix(css): don't re-run lightningcss visitor during minify (fix #23146) (#23147)15f0307fix(build): make client chunkImportMap work withsharedPlugins: true(#23184)c2155fetest(bundled-dev): enable sourcemap playgrounds (#23080)ef02435docs(build): fix incomplete@defaultfor build.minify (#23177)eac0cc8fix(bundled-dev): inject client script tag before chunk scripts (#23161)23b8a08refactor(bundled-dev): avoid injecting server values in the bundle (#22967)e72036erefactor(bundled-dev): remove rolldown lazy stub module workaround (#23129)14454fdfix(deps): update all non-major dependencies (#23136)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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