Skip to content

v0.9.1 — SQL-prose false positives, nested-source-root Python imports

Choose a tag to compare

View all tags
@einvoice-dev1 einvoice-dev1 released this 25 Jul 01:55
· 2 commits to main since this release
v0.9.1
e6c5df6

Fixes

  • SQL-literal detection no longer misfires on ordinary prose. Strings like "Select a model", "Explicitly select terminal rendering", or "Could not update detection rule" were being read as raw SQL. The heuristic now requires an UPDATE to have a real SET clause and a SELECT to have a real FROM clause (with the entity extracted from that clause, not guessed from the first token) — bounded to the actual containing string/line, not scanned hundreds of lines ahead. Verified on the PetClinic benchmark: a garbled ptype data-store entity is now correctly PetType; on Dreamhouse LWC, a spurious single-letter a entity is gone and conformance ticks up from 95.3% to 95.9%.
  • Python absolute imports below a nested source root now resolve. tools/python/mypkg/api.py importing mypkg.store (where tools/python is the real sys.path root, common in monorepos) previously stayed unresolved/external. Resolution is conservative: only a unique unambiguous path-suffix match resolves — if two packages could plausibly satisfy the same dotted import, it correctly stays external rather than guessing.
  • Intel macOS installs stay on a working cryptography wheel. Pinned cryptography<49 so pip install archsteer doesn't fall back to a Rust source build on Intel Macs, where a compatible prebuilt wheel exists on the 48.x line.
  • README: clarified the local first-run flow and where to send feedback.

Validation

40 tests (up from 34), all passing. Spring PetClinic and trailheadapps/dreamhouse-lwc benchmarks re-verified — no regressions, and the SQL-prose fix visibly cleans up both.

Full diff: v0.9.0...v0.9.1

Assets 2
Loading