Skip to content

InferBridge 0.11.0-beta.1

Pre-release
Pre-release

Choose a tag to compare

@Quazmoz Quazmoz released this 18 Sep 16:10
· 57 commits to main since this release

InferBridge 0.11.0-beta.1

Fixes two issues reproduced during local OpenVINO hardware testing and rebuilds the beta.

Fixes

  • Prevents HTTP 500 after NPU stream cancellation by waiting for engine recovery before prompt construction and token accounting. Applies the same model lease to Responses requests, tool retries, and context-budget inspection, and retains it until cancelled tokenizer workers finish.
  • Prevents GenAI from applying a second chat template to already formatted prompts, which could exceed the NPU prompt limit even when the app's token budget passed.
  • Makes the Benchmark Lab browser regression select CPU explicitly so it works on machines with GPU and NPU devices as well as CPU-only CI workers.
  • Removes a live Hugging Face dependency from the custom embedding registration unit regression; access checks remain covered separately.
  • Skips the real Hugging Face progress-bar regression when optional conversion dependencies are absent in minimal-runtime CI; qualified Windows builds still execute it.
  • Retains the active Hugging Face download progress and preparation watchdog fix from 0.11.0-beta.

Validation and compatibility

  • Local source validation: 1,333 unit tests passed, 20 skipped; 39 Chromium browser checks passed.
  • Ruff lint, formatting, dependency consistency, and all 37 injected JavaScript blocks passed.
  • Fixes Windows certification report generation when a device is unavailable or its server fails to start.
  • Existing settings, model files, downloaded caches, and data schema remain compatible.
  • Real CPU, GPU, and NPU API and prompt-capacity checks passed on the local validation machine. GPU compiled-cache reuse failed its fingerprint check and remains unverified.
  • See docs/certification/LOCAL_AUDIT_2026_09_18.md for hardware results and verification limits.
  • This beta is unsigned and makes no Authenticode signing claim.