Skip to content

Foundry IQ Live Knowledge Sources Accelerator v2.0.0

These candidate notes describe the first semantic-version product release contract for the accelerator. The version follows the existing LiveKS v2 and azd template 2.0.0 history. The earlier walkthrough-v1 tag remains a separate media/documentation release and is not reclassified.

Expected tag: v2.0.0.

Highlights

  • Plan-first offline, search-index, mcp-search-index, three-source, mcp-only, byo-fabric, and full profiles.
  • Separate GA Azure AI Search 2026-04-01 and public-preview 2026-05-01-preview API contracts.
  • Deterministic source packaging from tracked, allowlisted public files.
  • Versioned synthetic scenario packs with deterministic replay evidence and legacy try aliases.
  • Internal provider operation boundaries for current Search Index, MCP Server, native Fabric Ontology, and Knowledge Base paths, while lifecycle ownership and evidence policy remain centralized.
  • A lifecycle-independent, environment-configured Knowledge Base MCP consumer with JSON/SSE protocol parity, mandatory known-fact validation, and sanitized evidence.
  • SHA-256 checksums, a machine-readable file manifest, and an SPDX 2.3 SBOM validated by spdx-tools.
  • Full-commit-SHA GitHub Action pinning, explicit least-privilege permissions, and guarded tag publication.

Candidate Artifacts

  • azure-ai-search-foundry-iq-live-knowledge-sources-v2.0.0.tar.gz
  • azure-ai-search-foundry-iq-live-knowledge-sources-v2.0.0-manifest.json
  • azure-ai-search-foundry-iq-live-knowledge-sources-v2.0.0-sbom.spdx.json
  • azure-ai-search-foundry-iq-live-knowledge-sources-v2.0.0-SHA256SUMS.txt

The dry run creates these files only under ignored .release/ paths. It does not create tag v2.0.0, publish a GitHub Release, upload production artifacts, publish a registry package or installer, or create a production attestation. Publication remains blocked until the release authority is marked ready with a release date and a trusted Microsoft repository tag points to the exact main commit.

Compatibility Boundary

The release artifact records the digest of config/compatibility.yaml; it does not broaden that contract. CI-proven runtimes, unverified combinations, public-preview caveats, and Azure/Fabric live evidence remain documented in API Compatibility.