Skip to content

[BUG] apm deps list exits 0 on a lockfile with merge conflict markers, and apm prune blames apm.yml #3695

Closed

Description

Describe the bug

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/lockfileLockfile schema, per-file provenance, integrity hashes, drift detection.pillar/foundationsPillar: reliability, platforms, CI, code healthpriority/lowHuman-set low priority; does not imply acceptance, implementation approval or a release target.type/bugSomething does not work as documented.

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions