Skip to content

Add custom linter to enforce config version import chain#2225

Merged
dgageot merged 1 commit intodocker:mainfrom
dgageot:board/custom-linter-for-codebase-constraints-a5566d20
Mar 23, 2026
Merged

Add custom linter to enforce config version import chain#2225
dgageot merged 1 commit intodocker:mainfrom
dgageot:board/custom-linter-for-codebase-constraints-a5566d20

Conversation

@dgageot
Copy link
Member

@dgageot dgageot commented Mar 23, 2026

Let's try to implement project-specific rules with rubocop-go

This first check ensures that config version packages (pkg/config/vN) only import their immediate predecessor. This prevents accidental version skipping or importing pkg/config/latest from frozen versions.

This is totally experimental

Assisted-By: docker-agent

@dgageot dgageot requested a review from a team as a code owner March 23, 2026 11:45
docker-agent[bot]

This comment was marked as outdated.

@dgageot dgageot force-pushed the board/custom-linter-for-codebase-constraints-a5566d20 branch from 487386f to e1f3202 Compare March 23, 2026 13:48
Introduce a project-specific linter using rubocop-go that ensures config version packages (pkg/config/vN) only import their immediate predecessor. This prevents accidental version skipping or importing pkg/config/latest from frozen versions.

Assisted-By: docker-agent
@dgageot dgageot force-pushed the board/custom-linter-for-codebase-constraints-a5566d20 branch from e1f3202 to 6c810bf Compare March 23, 2026 14:17
@dgageot dgageot merged commit 3336e23 into docker:main Mar 23, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants