Skip to content

Remove obsolete Compose version field #149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aidankhogg merged 1 commit into from
Jun 29, 2026
Merged

Remove obsolete Compose version field #149

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,3 @@
version: "3.8"

# Full NetEngine local bootstrap stack.
# Services here start BEFORE `netengine up` runs.
# CoreDNS and step-ca are deployed by phase handlers at runtime.
Expand Down
2 changes: 1 addition & 1 deletion docs/compose-brainstorm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,4 +235,4 @@ services:
- [ ] Should we provide `compose.override.yml` as a git-ignored template?
- [ ] Do we want dedicated profiles for: `debug`, `load-test`, `chaos`, `security`?
- [ ] Should multi-world compose use separate networks or shared?
- [ ] Should we version compose file format or stick to 3.8+?
- [x] Omit the obsolete top-level Compose file `version` field and rely on the Compose Specification.