You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by "Shaurya2k06 (via GitHub)" <gi...@apache.org> on 2026/07/27 10:59:14 UTC

[PR] fix(tools/security-tracker-stats-dashboard): align Python floor to 3.11 [magpie]

Shaurya2k06 opened a new pull request, #968:
URL: https://github.com/apache/magpie/pull/968

   ## Summary
   
   - Align `requires-python`, ruff `target-version`, and mypy `python_version` in `tools/security-tracker-stats-dashboard` to the repo-wide **3.11** floor (they previously disagreed: 3.9 / py39 / 3.10).
   - Update the README Runtime prerequisite to Python 3.11+ and refresh the tool `uv.lock` header.
   - Apply the py311 ruff fixes the raised target now surfaces (`datetime.UTC` / `zip(..., strict=True)`).
   - Re-lock root `uv.lock` `mypy` `requires-dev` specifiers to `>=2.3.0` so `prek` stops rewriting the lock when this tool's README is touched (same correction as #965 — drop that hunk if #965 lands first).
   
   ## Type of change
   
   - [ ] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
   - [ ] Tool / bridge contract (`tools/<system>/*.md`)
   - [x] Python package (`tools/*/` with `pyproject.toml`)
   - [ ] Groovy reference impl
   - [ ] Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
   - [x] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
   - [ ] Project template (`projects/_template/`)
   - [ ] CI / dev loop (`prek`, workflows, validators)
   - [ ] Other:
   
   ## Test plan
   
   - [x] `prek` commit hooks pass on the changed files
   - [x] `uv run --directory tools/security-tracker-stats-dashboard --group dev pytest` — 114 passed
   - [x] `uv run --directory tools/security-tracker-stats-dashboard --group dev ruff check` / `mypy` — clean
   - [ ] For Groovy bridges touched: command-line invocation tested end-to-end
   - [ ] For skill changes: eval suite passes for the affected skill
   - [ ] For skill *behaviour* changes: a new or updated eval fixture is included in this PR
   - [ ] Other:
   
   ## RFC-AI-0004 compliance
   
   - [ ] **HITL** — any new mutation is gated on explicit user confirmation
   - [ ] **Sandbox** — no new unrestricted host access; network reach declared in the adapter
   - [x] **Vendor neutrality** — placeholders used in skill / tool prose (N/A for this version-floor change)
   - [ ] **Conversational + correctable** — agentic-override path documented if behaviour is adopter-tunable
   - [ ] **Write-access discipline** — no autonomous outbound messages; drafts only, sent on confirmation
   - [ ] **Privacy LLM** — private content does not reach a non-approved LLM; redactor invoked where needed
   
   ## Linked issues
   
   Closes #948
   
   ## Notes for reviewers (optional)
   
   If #965 merges first, rebase and drop the root `uv.lock` hunk — it is only included so `prek`'s vendor-neutrality hook does not fail this branch on README touch.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(tools/security-tracker-stats-dashboard): align Python floor to 3.11 [magpie]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #968:
URL: https://github.com/apache/magpie/pull/968


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org