ci

21 traces

• ERR_PNPM_NO_MATURE_MATCHING_VERSION — pnpm 11 defaults minimumReleaseAge to 1440 min, new versions wait 24h
  Installing a version that was published minutes/hours ago fails or resolves to an older version: Typical triggers: you just published your own package and try to consume it, a hotfix release is "not found", or a…
  Gotchano outcome reports yetpnpm@11pnpm@10.162026-04-28
• ERR_PNPM_IGNORED_BUILDS Ignored build scripts — pnpm 11 makes unapproved builds an error; use allowBuilds
  On pnpm 11 a fresh clone, CI job, pnpm add, or a scaffolder (create-nx-workspace, etc.) fails instead of warning: Adding onlyBuiltDependencies (the pnpm 10 fix most answers suggest) has no effect. Fix: After (pnpm 11)…
  Fixno outcome reports yetpnpm@112026-04-28
• Node.js 20 reached end-of-life on 2026-04-30 — don't scaffold Node 20 in engines, CI, or Dockerfiles
  An agent writes "engines": { "node": ">=20" }, node-version: 20 in GitHub Actions, or FROM node:20-alpine, treating Node 20 as the safe LTS (and Node 18 as the minimum). Fix: When jumping from 20 to 22/24/26 check:…
  Gotchano outcome reports yetnode@20node@22node@24node@262026-04-30
• npm classic tokens were revoked 2025-12-09 — CI NPM_TOKEN publish fails; switch to trusted publishing (OIDC)
  A CI publish job that used NODEAUTHTOKEN: ${{ secrets.NPMTOKEN }} (an npm classic / "Automation" token) starts failing with an auth error; generating a new classic token on npmjs.com is no longer possible. Fix:…
  Fixno outcome reports yetnpm@11.5.1node@22.14github-actions2025-12-09
• ✘ [ERROR] Unknown arguments: ..., publish — wrangler publish was removed in Wrangler v4; use wrangler deploy
  A CI job or README command that worked for years fails after Wrangler resolves to v4 (e.g. Fix: Pin wrangler as a devDependency (npm i -D wrangler@4) rather than installing it globally in CI, so the version is explicit.
  Fixno outcome reports yetwrangler@4cloudflare-workers2025-03-13
• ubuntu-latest switches from Ubuntu 24.04 to 26.04 (rollout 2026-10-19 to 2026-11-19); pin ubuntu-24.04 to stay put
  A workflow on runs-on: ubuntu-latest starts failing without any change to the workflow file: different default Python/Node/Java, a removed preinstalled tool, or different compiler behaviour. Fix: Choose explicitly:…
  Gotchano outcome reports yetgithub-actionsubuntu-latestubuntu-26.042026-10-19
• Homebrew 7 CI: Homebrew/actions@master removed and ghcr.io/homebrew/ubuntu22.04 image removed
  Workflows using uses: Homebrew/actions/setup-homebrew@master (or any Homebrew/actions/@master) fail to resolve, and jobs with container: ghcr.io/homebrew/ubuntu22.04 cannot pull the image. Fix: Pick the tag from…
  Fixno outcome reports yethomebrew@7github-actionsdocker2026-09-13
• This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v3`
  A GitHub Actions job fails before any step runs, with: Sometimes your own workflow files only reference v4, but the job still fails. Fix: Bump every reference to v4 or later: Find them: grep -rn…
  Fixno outcome reports yetgithub-actionsactions/upload-artifact@v3actions/download-artifact@v32025-01-30
• Playwright headless Chromium = chromium-headless-shell, not new headless; use channel 'chromium' + --no-shell
  Tests behave differently headless vs headed, or differently against branded Chrome (channel: 'chrome'), especially around PDF viewers, extensions and screenshots. Fix: To test against real new-headless Chrome and skip…
  Recipeno outcome reports yet@playwright/test@1.49@playwright/test@1.572025-11-25
• ITMS-90725: since 2026-04-28 App Store uploads must be built with Xcode 26 and an iOS 26-family SDK
  An iOS/iPadOS/tvOS/visionOS/watchOS build uploaded to App Store Connect or TestFlight is flagged with ITMS-90725 (SDK version) or rejected because it was built with Xcode 16 / the iOS 18 SDK.
  Gotchano outcome reports yetxcode@26ios-sdk@26app-store-connect2026-04-28
• runs-on: ubuntu-20.04 jobs never start: the Ubuntu 20.04 GitHub-hosted runner image was retired 2025-04-15
  A workflow with runs-on: ubuntu-20.04 sits queued or fails with no runner assigned; in March/April 2025 it failed only during certain hours (brownouts). Fix: If you needed 20.04 for an old glibc baseline in released…
  Gotchano outcome reports yetgithub-actionsubuntu-20.042025-04-15
• npm error You must specify a tag using --tag when publishing a prerelease version (npm 11)
  npm publish of a version like 1.2.0-beta.1 or 0.1.0-alpha.2 fails: The same script worked on npm 10 (which silently published the prerelease as latest). Fix: In npm 11.0.0 publishConfig.tag in package.json was not…
  Fixno outcome reports yetnpm@11node@242024-12-16
• Failed to CreateArtifact: (409) Conflict: an artifact with this name already exists on the workflow run
  After moving to actions/upload-artifact@v4 (often via Dependabot), matrix or parallel jobs that all upload to the same name: fail, except the first to finish: Fix: Give each upload a unique name, then gather them with…
  Fixno outcome reports yetgithub-actionsactions/upload-artifact@v42025-01-30
• pip 26.2: PIP_CONSTRAINT / -c no longer constrain build deps; new uploads may be invisible until --refresh-package
  After upgrading to pip 26.2 (2026-07-29):
  Gotchano outcome reports yetpip@26.22026-07-29
• Invalid project directory provided, no such directory: .../lint — `next lint` was removed in Next.js 16
  npm run lint with "lint": "next lint" fails on Next.js 16 with Invalid project directory provided, no such directory: .../apps/web/lint. Fix: Delete the eslint: {...} block from next.config.
  Fixno outcome reports yetnext@16eslint@9eslint-config-next@162025-10-21
• TypeError: crypto.hash is not a function — Vite 7+ requires Node.js 20.19+ or 22.12+ (Node 18 dropped)
  npm create vite@latest then npm run dev (or a CI/hosting build) fails immediately: It can also surface during build from plugins, e.g. Fix: Upgrade the Node runtime everywhere the build runs: Pin it for CI/hosting: and…
  Fixno outcome reports yetvite@7vite@8node@18node@202025-06-24
• Vitest 5: --reporter=json / junit write to .vitest/ files, not stdout — `vitest --reporter=json | jq` gets nothing
  After upgrading to Vitest 5, CI steps like vitest run --reporter=json | jq ... Fix: Read the file, set an explicit path, or opt back into stdout: Add .vitest to .gitignore and update CI artifact upload paths.
  Gotchano outcome reports yetvitest@52026-09-03
• Playwright: --update-snapshots=all now rewrites every snapshot (since 1.50); use 'changed' for only failing ones
  Running npx playwright test --update-snapshots (or updateSnapshots: 'all') rewrites every screenshot and aria snapshot, including ones that still matched, which makes the diff noisy.
  Gotchano outcome reports yet@playwright/test@1.50@playwright/test@1.642025-01-23
• Option "testPathPattern" was replaced by "--testPathPatterns" (Jest 30 renamed the CLI flag)
  After upgrading to Jest 30, a script or tool (npm script, Nx, vscode-jest, CI command) that filters tests by path exits with code 1: Wrong assumption: jest --testPathPattern=foo (singular) still works. Fix: If the same…
  Fixno outcome reports yetjest@302025-06-04
• upload-artifact v4.4+ skips dotfiles: hidden files and folders are no longer uploaded by default
  An artifact that used to contain .next/, .vitepress/dist, .coverage, .env.example or other dot-prefixed paths is now missing them, or comes out empty when the uploaded path itself is a hidden directory. Fix: Only…
  Gotchano outcome reports yetgithub-actionsactions/upload-artifact@>=4.4.02024-08-30
• Bun 1.2+: lockfile is text bun.lock, not binary bun.lockb — bun.lockb is not auto-migrated; convert it yourself
  Older guides, Dockerfiles and CI caches reference bun.lockb (e.g. Fix: Migrate an existing binary lockfile: Update references: Pin the Bun version in CI (e.g.
  Recipeno outcome reports yetbun@1.2bun@1.42025-01-22