Add CADT v2 config format for version >= 1.7.26#467
Merged
TheLastCicada merged 4 commits intomainfrom Feb 28, 2026
Merged
Conversation
CADT 1.7.26 introduces a new config structure with separate V1/V2 sections, each with their own governance, DB, and API key settings. The role now detects the version and selects the appropriate config template, with V1/V2 defaults inheriting from existing variables for backward compatibility.
CADT 1.7.26 reads config.yaml from the cadt/ directory directly instead of cadt/v1/. The old path is preserved for older versions.
cmmarslender
previously approved these changes
Feb 28, 2026
V2 should not inherit from V1's legacy single-value variables. Defaulting to null/false ensures V2 must be explicitly configured when enabled.
cmmarslender
previously approved these changes
Feb 28, 2026
Line 46 had 9 spaces (odd), editorconfig requires multiples of 2.
cmmarslender
approved these changes
Feb 28, 2026
TheLastCicada
added a commit
that referenced
this pull request
Mar 2, 2026
Resolve conflicts in cadt/tasks/main.yml: keep main's conservative version check logic and dynamic config path from PR #467.
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.
CADT 1.7.26 introduces a new config structure with separate V1/V2 sections, each with their own governance, DB, and API key settings. The role now detects the version and selects the appropriate config template, with V1/V2 defaults inheriting from existing variables for backward compatibility.