deps: bump github.com/compose-spec/compose-go/v2 from 2.14.0 to 2.15.0 - #132
Conversation
Bumps [github.com/compose-spec/compose-go/v2](https://github.com/compose-spec/compose-go) from 2.14.0 to 2.15.0. - [Release notes](https://github.com/compose-spec/compose-go/releases) - [Commits](compose-spec/compose-go@v2.14.0...v2.15.0) --- updated-dependencies: - dependency-name: github.com/compose-spec/compose-go/v2 dependency-version: 2.15.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Code Review — c21f999 · CLEAN
Routine Dependabot bump of compose-go/v2 2.14.0 → 2.15.0, and it is clean. I read the full upstream tag-compare (22 commits) and verified every API this repository consumes survives intact: the cli option functions and ProjectFromOptions used by compose/load.go, and the types package surface (Project, ServiceConfig, ServiceVolumeConfig, MappingWithEquals, Labels, ShellCommand, DeployConfig, Resources, Secrets) used across compose/ and up.go. The upstream changes are bug fixes (diamond-include re-merge, override merge panics, a data race in WithServicesTransform, version-warning race) plus additive API; the one strictness change (GetPullPolicy now errors on unrecognized values) is in code this repository never calls. The go.sum deltas (testify, logrus, dropped go-spew/go-difflib) match the upstream dependency-cleanup commit in this range, and compose-go's go 1.24 requirement fits this repo's go 1.25.0. No findings.
What I reviewed
Coverage notes: start_review resolved a directives base SHA, but .dap/code-review.yml does not exist at that commit, so I reviewed against the core prompt alone with no repository-specific bug shapes. I verified compatibility by reading the upstream diff via the GitHub API rather than downloading the module or building — a go build/go test run by a human would confirm compilation, which I could not execute under review rules. Conditional dimensions (redelivery, state-integrity, operability, etc.) do not apply: the change touches only go.mod and go.sum.
CLEAN — this round found nothing. Reply in a finding's own thread to argue it. On the pull request I answer @dap-code-review-by-crunchloop review, pause and resume.
Bumps github.com/compose-spec/compose-go/v2 from 2.14.0 to 2.15.0.
Release notes
Sourced from github.com/compose-spec/compose-go/v2's releases.
Commits
4ddbf11cli: validate COMPOSE_FILE entries point to actual compose files500d50cfix: merge attributes of repeated variable occurrences in ExtractVariables57f6c16tests: run named table cases as subtests261851bloader/tests: completeness test keeps the conformance matrix exhaustive3843a20loader/tests: link every attribute file to the spec section it locks728b3f2loader/tests: loadsAs expresses expectations as canonical YAMLf8211c4docs: TESTING.md codifies the testing contract95dbfdftest: cover short/long ulimit syntax combinations in override merge5a10b5afix: ignore default .env probe on permission deniedf0442fffix(types): reject unrecognized pull_policy values instead of defaultingDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)