v3.4.3
Component versions
| Component | Version |
|---|---|
gpt-rag (platform) |
v3.4.3 |
gpt-rag-ui |
v2.3.13 |
gpt-rag-orchestrator |
v3.4.1 |
gpt-rag-ingestion |
v2.4.14 |
infra / AI Landing Zone |
v2.3.0 |
User and operator impact
Fixes the Fabric Data Agent knowledge source support that v3.4.2 advertised. In v3.4.2 the platform-side wiring (App Configuration keys, search.j2 knowledge source block, search.settings.j2 bindings, postProvision.ps1 passthrough) was correct and the knowledge source registers against Foundry IQ 2026-05-01-preview. However manifest.json pinned the orchestrator to v3.4.0, and the Fabric Data Agent retrieve wiring (kind=fabricDataAgent, per-user OBO forwarding, dataAgentAnswer normalization) actually landed on the orchestrator branch a few minutes after that tag was cut. As a result, v3.4.2 deployments that flipped FABRIC_DATA_AGENT_ENABLED=true had the knowledge source registered in Foundry IQ but the deployed orchestrator container did not append it to knowledgeSourceParams at retrieve time, so no Fabric Data Agent grounding actually occurred.
v3.4.3 bumps the orchestrator pin to v3.4.1, which is the tag that actually contains the Fabric Data Agent retrieve code. No template, script, or App Configuration changes are needed; existing v3.4.2 environments only need to redeploy the orchestrator container to pick up the fix.
Changed
manifest.json: orchestrator pin bumped fromv3.4.0tov3.4.1.
Fixed
- Fabric Data Agent knowledge source now actually works end to end when
FABRIC_DATA_AGENT_ENABLED=true. Thev3.4.2platform release registered the knowledge source in Foundry IQ but pinned an orchestrator (v3.4.0) that had no code to consume it at retrieve time.v3.4.3pins orchestratorv3.4.1which carries the retrieve wiring.