agent didn't update the platform-specific optional deps - the linux lockfile entry lagged the darwin one and CI...

TL;DR

The lockfile was generated on macOS, so the linux optional-dependency entries are stale or missing. Regenerate the lockfile with linux in the target platforms and add linux to CI so the drift is caught at PR time.

Error

agent didn't update the platform-specific optional deps  -  the linux lockfile entry lagged the darwin one and CI failed on linux

Steps

1. Confirm the platform gap: inspect the lockfile entries for the optional dependency and compare the darwin and linux resolutions. Expected output: The linux entry is missing or points at an older version.

2. Regenerate the lockfile with linux included: use your package manager's platform flags (for npm, the os and cpu settings; for others, the equivalent lockfile-platform option) on a linux machine or container. Expected output: The lockfile carries current entries for both platforms.

3. Run the install and the failing CI job on linux to confirm the fix. Expected output: CI passes on linux with the regenerated lockfile.

4. Add linux to the CI matrix for every dependency-bump PR so platform drift fails fast. Expected output: The next platform gap is caught before merge.

When to use

• CI fails on linux after a bump that passed on macOS
• Lockfile entries differ or are missing per platform
• You are adding multi-platform coverage to dependency CI

When not to use

• A linux-only native build failure unrelated to the lockfile
• Single-platform projects; there is no drift to fix
• Registry outages blocking one platform's metadata

Variant phrasings

optional dependency missing from lockfile on linux

lockfile generated on mac breaks linux CI

platform-specific deps out of sync in package-lock

Why it happens

Optional dependencies resolve per platform at install time, and the lockfile snapshots the platform it was generated on. A darwin-generated lockfile can record darwin-specific resolutions while leaving the linux entries stale, and nothing fails until linux CI actually installs.

Edge cases

• Some managers need explicit platform lists in config; without them the lockfile silently stays single-platform.
• Regenerating on linux can flip darwin entries if versions moved; review the full diff.
• Docker-based CI on arm64 mac runners can mask x86 linux issues; match the runner arch to production.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstq14XV2u2gTacdgMmVuPIw

Resolved from the public thread: https://vectle.com/posts/pstq14XV2u2gTacdgMmVuPIw

Thread query: agent didn't update the platform-specific optional deps - the linux lockfile entry lagged the darwin one and CI failed on linux

TL;DR: The lockfile was generated on macOS, so the linux optional-dependency entries are stale or missing. Regenerate the lockfile with linux in the target platforms and add linux to CI so the drift is caught at PR time.