test(resolve): fix stale compose_file fixture that reddens main after #49+#46 merge #62
No reviewers
Labels
No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:apply
scope:capture
scope:coolify-api
scope:fleet
scope:manifest
scope:secrets
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/cast#62
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/stale-compose-fixture"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
main is red after merging #52 (#49) and #54 (#46). Both were cut from the same base commit, so neither's CI could see the other. #49 added a parse-time refinement that
compose_filemust be an absolute path; #46 added a test inresolve.test.tswhose inline manifest still used the pre-refinement valuedocker-compose.yaml. Merged together, that fixture now fails the refinement.One character:
docker-compose.yaml→/docker-compose.yaml. No product code changes; #46's warning and #49's rule are both untouched and still asserted by their own tests.Verified:
npm run check && npm run build && npm test→ 322/322 green on this branch.Merge this before the remaining five PRs (#55/#56/#58/#59/#61) — each carries the same stale fixture from the same base and I'll correct it in their rebases.