Merge pull request #423 from BentoBoxWorld/fix/e2e-pin-mineflayer

Fix E2E CI: pin mineflayer via committed lockfile (1.21.11 support)

Author: tastybento

.github/workflows/e2e.yml

@@ -57,7 +57,9 @@ jobs:
         uses: actions/cache@v4
         with:
           path: e2e/src/test/e2e/node_modules
-          key: e2e-npm-${{ hashFiles('e2e/src/test/e2e/package.json') }}
+          # Key on the committed lockfile so the cache tracks the exact resolved versions
+          # (mineflayer/minecraft-data must support the target Minecraft version).
+          key: e2e-npm-${{ hashFiles('e2e/src/test/e2e/package-lock.json') }}
 
       - name: Build Challenges jar (Maven)
         run: mvn -B -DskipTests package

e2e/.gitignore

@@ -8,4 +8,5 @@ build/
 # Node / TypeScript test artifacts
 src/test/e2e/node_modules/
 src/test/e2e/dist/
-src/test/e2e/package-lock.json
+# package-lock.json IS committed — it pins mineflayer/minecraft-data to versions that
+# support the target Minecraft version, so CI installs are reproducible.