Update Compose Spec to v2 - #68
Merged
Merged
Conversation
To support the latest Composefile syntax features
qezz
approved these changes
Jul 15, 2026
qezz
left a comment
Contributor
There was a problem hiding this comment.
thanks for looking into it
1/5: maybe we can throw in a test for the env_file, just a simple one
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To support the latest Composefile syntax features. More specifically, I'm interested in supporting
env_files being optional:which currently crashes with:
V2 has been chosen since the spec update I required first landed in v2.0.0-beta.2. Finally, instead of refactoring the entire codebase adding Context support to the functions working with Composefiles, I opted to use
context.Background(), which was also the default fallback when first adding Context support upstream (compose-spec/compose-go@ad9be94).