Skip to content

fix: resolve Mineflayer uuid security update - #32

Merged
TWME-TW merged 1 commit into
TWME-TW:masterfrom
twme-ai:fix/mineflayer-uuid-advisory
Aug 12, 2026
Merged

fix: resolve Mineflayer uuid security update#32
TWME-TW merged 1 commit into
TWME-TW:masterfrom
twme-ai:fix/mineflayer-uuid-advisory

Conversation

@twme-ai

@twme-ai twme-ai commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Problem

The post-merge Dependabot security update for integration/mineflayer failed because Mineflayer 4.37.1 has two transitive uuid constraints:

  • @azure/msal-node@2.16.3 requires uuid ^8.3.0
  • yggdrasil@1.8.0 requires uuid ^10.0.0

The patched version is uuid 14.0.0+. Dependabot cannot find a safe update path and reports a downgrade to Mineflayer 1.4.0 as its only fix.

Fix

  • add package-scoped npm overrides for the two affected dependency edges, pinning uuid@14.0.1
  • regenerate the lockfile so both consumers share the patched package
  • add a normal CI job that runs npm ci and npm audit for the Mineflayer integration

The override is scoped to the packages identified by the advisory rather than globally forcing unrelated future dependencies.

Verification

  • npm ci: passed
  • npm audit --audit-level=low: 0 vulnerabilities
  • npm ls: both @azure/msal-node and yggdrasil resolve uuid@14.0.1
  • CommonJS consumers load and generate valid UUIDs
  • mvn -B clean verify: passed
  • ./integration/mineflayer/run-e2e.sh: passed on Paper 1.21.11
  • actionlint: passed

@TWME-TW
TWME-TW merged commit 5a90a2e into TWME-TW:master Aug 12, 2026
2 checks passed
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.

2 participants