feat(config): freeze v15 and start v16 as latest - #4170
Merged
Conversation
Assisted-By: docker-agent
gtardif
approved these changes
Sep 4, 2026
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
2 participants
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.
The config versioning process requires that once a schema version is stable, it gets frozen as an immutable, numbered package so downstream upgraders can rely on it forever. This PR freezes
pkg/config/latestaspkg/config/v15and advanceslatestto begin work on v16.pkg/config/v15is a snapshot of the current latest package with the package name updated tov15. Itsparse.gostill referencesv14for the upgrade path, preserving the existingv14→v15upgrader chain. The newpkg/config/latest/parse.gonow importsv15as its predecessor, andlatest/types.gobumpsVersionto"16".pkg/config/versions.goregistersv15beforelatestso the version resolution order stays correct.agent-schema.jsonis updated to describe Docker Agent v16 and includes"16"in its version enum and examples.No behaviour changes at runtime — existing configs continue to load through the same upgrade chain, and v16 is a clean slate for future schema additions.