Skip to content

InferBridge 0.10.0-beta.1

Pre-release
Pre-release

Choose a tag to compare

@Quazmoz Quazmoz released this 17 Sep 15:14
· 137 commits to main since this release

InferBridge 0.10.0-beta.1

InferBridge 0.10.0-beta.1 is the first beta after 0.9.6. It expands the hardware-advisor workflow into a Benchmark Lab, strengthens benchmark evidence and resource-safety handling, improves model recovery and storage resilience, and hardens the development and release qualification path.

This is a beta pre-release. Release artifacts may be unsigned; if they are unsigned, Windows may report an unknown publisher and SmartScreen may warn. Verify downloads against the published SHA-256 checksums.

Benchmark Lab and hardware guidance

  • Adds a dedicated Benchmark Lab in the browser UI for repeatable local model/device measurements.
  • Adds bounded benchmark requests, resource-safety checks, and regression coverage around benchmark execution.
  • Improves benchmark evidence persistence and ranking so recommendations distinguish measured local evidence from expected compatibility.
  • Refines hardware-advisor device profiles, automatic benchmark behavior, and profile ranking.
  • Adds Chromium behavior coverage for the Benchmark Lab.

Reliability and recovery

  • Improves model-recovery UI behavior and recovery-state handling.
  • Hardens storage-state handling and adds resilience coverage for damaged or partially written state.
  • Improves model-converter compatibility and associated regression coverage.
  • Extends model-resolution and advisor-evidence resilience tests.

API and integration quality

  • Extends OpenAI-compatible API behavior covered by the external contract smoke suite.
  • Adds Hermes Agent integration guidance and refreshes integration documentation.
  • Adds repository-level agent tooling guidance for supported coding assistants without changing InferBridge's runtime architecture.

Release and CI hardening

  • Keeps the pinned Windows release baseline separate from the latest-compatible dependency canary.
  • Exercises the source suite on Python 3.11 through 3.14, Chromium browser behavior, external API contracts, and Windows release/security harnesses.
  • Fixes the release publisher to target the canonical Quazmoz/InferBridge repository instead of the legacy pre-rename repository path.
  • Keeps the qualified OpenVINO release stack pinned; newer dependency stacks remain canary inputs until explicitly qualified.

Compatibility

  • Persistent data schema remains version 1.
  • Existing 0.9.6 models, settings, caches, browser state, benchmark evidence, and diagnostics remain compatible.
  • Installer identity and installation location remain unchanged for in-place upgrades.
  • OpenVINO GenAI remains the inference runtime. No Docker, Ollama, llama.cpp, GGUF, or cloud-inference dependency is introduced.

Qualification

The last code-changing development snapshot before this beta preparation passed the qualified Windows release baseline, latest-compatible Windows canary, external API contract smoke, Python 3.11-3.14 test matrix, Chromium browser behavior suite, and Windows release/security harness. The beta version and release-publisher corrections introduced during promotion preparation must also pass CI before the branch is promoted.

Mock and source validation do not prove physical-device behavior. Before stable promotion, validate a fresh install and in-place upgrade on real Windows hardware and confirm the available CPU/GPU/NPU paths with mock mode disabled. Authenticode claims are valid only when the signing gate succeeds.

Qualification status at publication

This unsigned beta was published at the maintainer's explicit request with known qualification failures. CPU qualification passed. GPU compiled-cache reuse failed in the full Windows harness; NPU cancellation recovery can cause subsequent Chat/Responses requests to fail with HTTP 500; AUTO lifecycle unload failed with HTTP 409. A correction is under review in #50 and is not included in these artifacts. Actual installer execution, clean-machine upgrade/uninstall, SmartScreen, and Authenticode trust were not verified.