You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] apm deps list exits 0 on a lockfile with merge conflict markers, and apm prune blames apm.yml #3695
Most commands (install, --frozen, audit --ci, outdated, lock, uninstall, update, deps why) reject an apm.lock.yaml that contains git conflict markers with an actionable error. apm deps list and apm deps tree exit 0 silently (they read apm_modules), and apm prune reports "Failed to parse apm.yml:" although apm.yml is valid and the lockfile is the broken file.
Expected behavior
All commands report the conflicted lockfile by name.
Found by the 0.36.0 pre-release lifecycle sweep, round 2 (#3649). Same behavior on v0.35.1, so this is not a 0.36 regression.
Activity
fix(deps): deps list, deps tree and prune name a conflicted lockfile (#…
fix: 0.36.0 red-team round 2 (MCP config safety, user-file collisions…
fix(tests): restore arm64 integration lanes for 0.36.0 (#3766)