Skip to content

deps: bump @devicefarmer/adbkit from 3.3.8 to 3.3.9 in the patch group - #9

Merged
cldmv-bot[bot] merged 1 commit into
nextfrom
dependabot/npm_and_yarn/next/patch-610d7ba14d
Aug 5, 2026
Merged

deps: bump @devicefarmer/adbkit from 3.3.8 to 3.3.9 in the patch group#9
cldmv-bot[bot] merged 1 commit into
nextfrom
dependabot/npm_and_yarn/next/patch-610d7ba14d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 5, 2026

Copy link
Copy Markdown
Contributor

Bumps the patch group with 1 update: @devicefarmer/adbkit.

Updates @devicefarmer/adbkit from 3.3.8 to 3.3.9

Release notes

Sourced from @​devicefarmer/adbkit's releases.

v3.3.9

What's Changed

Full Changelog: DeviceFarmer/adbkit@v3.3.8...v3.3.9

Commits

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 <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 patch group with 1 update: [@devicefarmer/adbkit](https://github.com/devicefarmer/adbkit).


Updates `@devicefarmer/adbkit` from 3.3.8 to 3.3.9
- [Release notes](https://github.com/devicefarmer/adbkit/releases)
- [Commits](DeviceFarmer/adbkit@v3.3.8...v3.3.9)

---
updated-dependencies:
- dependency-name: "@devicefarmer/adbkit"
  dependency-version: 3.3.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch
...

Signed-off-by: dependabot[bot] <support@github.com>

@cldmv-bot cldmv-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved by CLDMV-bot: patch bump from 3.3.8 to 3.3.9.

@cldmv-bot
cldmv-bot Bot enabled auto-merge August 5, 2026 12:29
@cldmv-bot cldmv-bot Bot added the type: dependencies Relates to dependency updates, version bumps, or package management label Aug 5, 2026
@cldmv-bot
cldmv-bot Bot merged commit 5a5fda3 into next Aug 5, 2026
24 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/next/patch-610d7ba14d branch August 5, 2026 12:31
Shinrai added a commit that referenced this pull request Sep 13, 2026
…ESOLVE

Dependabot's security-triggered PR #18 (@vitest/mocker 4.1.10->5.0.0)
targeted master directly instead of next -- GitHub's Dependabot always
opens security-update PRs against the default branch regardless of
target-branch config, bypassing the v4 staging flow same as the wisp
PR #9 incident. It was merged straight to master, diverging it from
next and leaving PR #10 (the persistent next->master release PR) in a
"dirty" (real conflict) state.

Bumping vitest's root package.json entry to satisfy @vitest/mocker's
constraint also left @vitest/coverage-v8 behind at ^4.1.10 -- the same
vitest5/coverage-v8 split ERESOLVE pattern hit ~10 other repos in this
fleet, just introduced here by Dependabot's own partial bump instead of
a separate PR. This means master's current committed state already
fails `npm ci` on a fresh clone, independent of this reconciliation.

Merged (not cherry-picked) so next inherits master's history properly,
and bumped @vitest/coverage-v8 to ^5.0.0 in the same commit so the
resolved state is installable. Verified: npm ci clean, 2/2 tests,
lint clean, format clean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: dependencies Relates to dependency updates, version bumps, or package management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants