Skip to content

ci(sonar): declare the qualified 3.13 and 3.14 interpreters to the analyzer - #1160

Open
doublewhy wants to merge 1 commit into
1152-sonar-mechanical-exemptionsfrom
fix/sonar-python-versions
Open

ci(sonar): declare the qualified 3.13 and 3.14 interpreters to the analyzer#1160
doublewhy wants to merge 1 commit into
1152-sonar-mechanical-exemptionsfrom
fix/sonar-python-versions

Conversation

@doublewhy

Copy link
Copy Markdown

Plain-language summary

  • Problem: sonar.python.version still declared 3.11, 3.12 after CI qualified CPython 3.13 and 3.14 (ci: qualify CPython 3.14 and bound interpreter support #1134), so the raes-strict gate analyzed the code with 3.12-era rules.
  • Fix: Declare the full supported range 3.11, 3.12, 3.13, 3.14 (the 3.11 floor still gates newer-syntax suggestions on the lint contract), and reclassify the properties file's identity digest.

Stacking

Based on 1152-sonar-mechanical-exemptions (PR #1155) so the digest classification stays coherent with that PR's properties edits; retargets to dev when #1155 merges and should be rebased then.

Heads-up for after merge

Sonar PR scans only report on changed lines, so this PR's own gate stays clean — but the next dev branch scan may surface findings that the newer-interpreter rules detect on existing code. If any appear, they'll show at https://sonarcloud.io/dashboard?id=Brad-Edwards_aces&branch=dev and should be triaged the same way as the #1152/#1153/#1154 slices.

Verification

  • Identity-cutover policy suite (46 tests) and tools/check_repo_policy.py pass with the reclassified digest.

🤖 Generated with Claude Code

…alyzer

sonar.python.version still said 3.11-3.12 after CI qualified CPython
3.13 and 3.14 (#1134), so the strictest gate analyzed the code with
3.12-era rules. Declare the full supported range; the 3.11 floor keeps
newer-syntax suggestions gated on the lint contract. The properties
file's identity digest is reclassified accordingly.

Note for the merge: the next dev branch scan may surface findings the
newer-interpreter rules detect on existing code; they would appear on
the dev analysis, not on this PR's changed-line scan.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

1 participant