#328 ci: add Python 3.13 to the test matrix

[Anonymous]

Originally created by: jasperdingg

Pull Request

Closes [#211]

Slice

• Repo: doberman-core
• Feature / Slice: [#211]
• Plan reference: Issue [#211]

What this PR does

• Adds Python 3.13 to the Ubuntu CI matrix
• Adds the Python 3.13 package classifier
• Keeps Python 3.11/3.12 support and the Windows 3.12 job unchanged

Tests added (run in CI)

• No new tests, the existing suite now runs on Python 3.13
• Local suite: 2530 passed, 6 skipped, 91.63% coverage

Public-release safety (doberman-core only)

• [x] Contains nothing from the "not allowed" list
• [x] Core builds, tests, and runs without the enterprise package

Security checklist

• [x] No runtime or guardrail behavior changed
• [x] No secrets or sensitive data committed
• [x] doberman-core does not import doberman_enterprise

Edge cases covered / Deviations from plan / Risks introduced

• No Python 3.13 compatibility fixes were required
• AI used to help testing / planning

[Anonymous]

Ticket changed by: fu351

• status: open --> closed

[Anonymous]

Originally posted by: fu351

Easiest merge of the week — two lines, exactly what [#211] asked for, and the 3.13 leg went green on the first run. Appreciated that you ran the full suite locally and put the numbers in the PR body, so the one question that mattered was already answered before I opened the diff. Thanks jasper!

If you're up for another tooling piece, [#195] (level-6) is a good one: a pre-commit config (ruff + lint-imports) so people catch locally in seconds what CI takes minutes to flag. Between the link checker, the entry-point test, and this, you already know where all those checks live.

[Anonymous]

Originally posted by: fu351

One thing I left out of the merge note: we have a Discord where the roadmap and design conversations happen between PRs. Four merged PRs in, every one making CI harder to fool, you'd be a welcome voice there. No obligation, of course; the issue threads always work too.