Skip to content

bidlint v1.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Aug 03:12
v1.0.0
b1bcfd1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

bidlint v1.0.0

Released 2026-08-21.

BidLint 1.0.0 is the first stable-contract release of the deterministic technical bid compliance engine.

Stable compatibility contract

The 1.x line now has an explicit compatibility floor covering:

  • public CLI commands and process exit codes;
  • report JSON required keys;
  • SourceRef, Requirement, VendorFact, and Finding required fields;
  • PASS / DEVIATION / MISSING / REVIEW finding semantics;
  • knockout status semantics;
  • deterministic compliance-score behavior;
  • semantic-versioning and backward-compatibility policy.

The machine-readable contract is available through bidlint.contracts.stable_contract_manifest() and is protected by regression tests.

Procurement workflow

The stable release includes the v0.8 procurement workflow:

  • explicit technical knockout criteria;
  • bidder clarification and unanswered requirement registers;
  • deviation and internal review queues;
  • procurement-ready ranking;
  • procurement-aware supplier-scorecard contract v2.

No commercial scoring, price preference, contractual acceptance, or implicit knockout inference is introduced.

Production hardening

The v0.9 hardening work is included in 1.0.0:

  • stable CLI error categories and exit codes;
  • malformed/adversarial PDF, XLSX, and IFC regression coverage;
  • wheel/sdist build and smoke-install validation on Python 3.11, 3.12, and 3.13;
  • runtime dependency security audit;
  • deterministic large-package benchmark with repeated output-digest verification.

The CI benchmark exercises 20,000 input facts and requires deterministic consolidation output under a deliberately broad regression ceiling.

Compatibility

BidLint 1.0.0 supports Python 3.11, 3.12, and 3.13.

Within the 1.x line, patch releases are intended for compatible fixes and minor releases may add backward-compatible surfaces. Removing, renaming, or semantically repurposing frozen contract elements requires a new major version.

See docs/STABLE_CONTRACT.md for the full compatibility policy.

Assets 2
Loading