Repository navigation
release: devkit extension 0.1.3 lockstep - #79
Conversation
release-devkit.yml validates pyproject == adapters/vscode package.json under devkit-v* tags. The 0.1.3 wheel bump left the extension at 0.1.2, failing validate. Extension code is unchanged since 0.1.2, but the lockstep contract requires the manifest to travel with the wheel.
|
devin-judge (ACP, high model): |
|
devin-judge (ACP, high model): |
drift-check failed: registry export moved install_spec poordjaevin -> devin-judge (post-shim). Manifest regenerated via tools/export_devkit_manifest.py.
|
devin-judge (ACP, high model): |
|
devin-judge (ACP, high model): |
|
devin-judge (ACP, high model): |
|
devin-judge (ACP, high model): |
|
Static scan (advisory) — result: Deterministic scan of 8 changed file(s) — gitleaks 8.30.1 · semgrep 1.182.1 · ruff 0.17.3. Findings are advisory evidence for the judge, not a lane verdict. gitleaks — 0 finding(s) semgrep — 0 finding(s) ruff (E9,F,S) — 75 finding(s)
|
AI Code Review Summary0 finding(s) across 0 reviewed file(s).
Top issuesNo issues found. LGTM ✅ Skipped files
Token usage: 0 in / 0 out. Reviewed by: ai-code-reviewer · ollama / qwen2.5-coder:1.5b |
devkit-v0.1.3 validate failed: wheel bumped to 0.1.3, extension manifest stayed 0.1.2. Lockstep contract requires both. Wheel already published on PyPI as 0.1.3.