chore: freeze config v12 and open v13 as latest#3753
Merged
Conversation
Assisted-By: docker-agent
aheritier
added
the
status/ready-for-review
gtardif
approved these changes
Jul 20, 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
3 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 schema is versioned so that agents pinned to an older format continue to parse correctly as the schema evolves. Periodically the current work-in-progress schema needs to be frozen into an immutable numbered package before new fields are added.
This commit freezes
pkg/config/latestaspkg/config/v12: the 16 source files are copied verbatim with the package declaration renamed tov12.pkg/config/versions.gois updated to register v12 in the upgrade chain. With v12 locked,latestis re-opened for v13 — theVersionconstant is bumped to"13"and the previous-version import inlatest/parse.gonow points atv12. The upgrader from v12 to v13 is intentionally a no-op at this point, ready for new fields to be layered on top.agent-schema.jsonfollows suit: the description is bumped to v13 and"13"is appended to the version enum and examples.No behaviour changes for existing agents; this is purely a schema bookkeeping step.