build(deps-dev): bump vitest from 3.2.4 to 3.2.6 in /apps/native - #582
build(deps-dev): bump vitest from 3.2.4 to 3.2.6 in /apps/native#582dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 to 3.2.6. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.6/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 3.2.6 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
attempt: df7cac5 #1 fixed — regenerated bun.lock and bun.nix for vitest 3.2.6, pushed 2c0c14c Diagnosis
Fix pushedCommit If this is attempt #2The danger job is fixed. The build and Storybook failures are infrastructure (transient network / missing secret) and need a re-run or a human to fix the GitHub App token secret — no further code changes should be needed. |
|
👀 CI is failing here (build, Storybook Snapshot Tests, danger) — on it. I may push a fix to this branch shortly; progress lands in the ci-fixer ledger comment. — sent by Claude (ci_fixer) |
Dependabot bumped vitest in apps/native/package.json but the lockfile was not regenerated, causing bun install --frozen-lockfile to fail in CI (danger job).
📋 PR Overview
|
🎨 Storybook previewUpdated for 2c0c14c |
Bumps vitest from 3.2.4 to 3.2.6.
Release notes
Sourced from vitest's releases.
Commits
b6d56f8chore: release v3.2.616f120dfix: pin last supported vite-node version2cbad0achore: release v3.2.5385a1aefix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...af88b1ffeat(api): addallowWriteandallowExecoptions toapi[backport to v3]...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.
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 this major versionwill 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 versionwill 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 dependencywill 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.