Skip to content

deps: bump github.com/compose-spec/compose-go/v2 from 2.14.0 to 2.15.0 - #132

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/compose-spec/compose-go/v2-2.15.0
Open

deps: bump github.com/compose-spec/compose-go/v2 from 2.14.0 to 2.15.0#132
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/compose-spec/compose-go/v2-2.15.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor

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.

v2.15.0

What's Changed

New Contributors

Full Changelog: compose-spec/compose-go@v2.14.0...v2.15.0

Commits
  • 4ddbf11 cli: validate COMPOSE_FILE entries point to actual compose files
  • 500d50c fix: merge attributes of repeated variable occurrences in ExtractVariables
  • 57f6c16 tests: run named table cases as subtests
  • 261851b loader/tests: completeness test keeps the conformance matrix exhaustive
  • 3843a20 loader/tests: link every attribute file to the spec section it locks
  • 728b3f2 loader/tests: loadsAs expresses expectations as canonical YAML
  • f8211c4 docs: TESTING.md codifies the testing contract
  • 95dbfdf test: cover short/long ulimit syntax combinations in override merge
  • 5a10b5a fix: ignore default .env probe on permission denied
  • f0442ff fix(types): reject unrecognized pull_policy values instead of defaulting
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Sep 7, 2026

@dap-code-review-by-crunchloop dap-code-review-by-crunchloop Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@dap-code-review-by-crunchloop dap-code-review-by-crunchloop Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No open findings on c21f999.

The DAP Code Review check run remains the verdict of record. This approval is dismissed if a finding reopens or a later head is not clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants