15 Commits

• Remove temperature from foundry hosting test (unsupported by CI model)

  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Giles Odigwe · 2026-04-29 15:31:57 -07:00
  3ab3370a8e
• Fix flaky integration tests and re-enable skipped tests

  - Foundry agent: add allow_preview=True to custom client test
  - Foundry hosting: raise max_output_tokens 50->200, add temperature,
    relax assertion in test_temperature_and_max_tokens
  - Foundry embedding: update skip reason with root cause (endpoint mismatch)
  - OpenAI file search: fix vector store indexing race condition by polling
    file_counts before querying; fix get_streaming_response -> get_response(stream=True)
  - Azure OpenAI file search: remove skip (transient 500 resolved)
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Giles Odigwe · 2026-04-29 15:06:17 -07:00
  072123a8f1
• Python: bump package versions for 1.2.2 release (#5561)

  * Python: bump package versions for 1.2.2 release
  
  PATCH bump (1.2.1 -> 1.2.2) for the released cohort. Five PRs land in this
  window:
  
  - agent-framework-openai: fix file_search citations breaking the assistant-
    message history roundtrip (#5557) — drives the released-tier PATCH
  - agent-framework-orchestrations: [BREAKING] standardize orchestration
    terminal outputs as AgentResponse (#5301)
  - agent-framework-core, agent-framework-declarative: preserve Workflow.run()
    shared state across calls, accept list[Message] in declarative start
    executor, and coerce Enum values when serializing PowerFx symbols (#5531)
  - agent-framework-foundry-hosting: add hosted Durable Workflow support
    (#5531)
  - agent-framework-azure-contentunderstanding: new alpha package — Azure AI
    Content Understanding context provider (#4829)
  - dependencies: workspace package dependency refresh (#5555)
  
  Per lockstep convention, all 21 beta packages stamp 1.0.0b260429 and all 4
  alpha packages (now including the new contentunderstanding) stamp
  1.0.0a260429. Date stamp reflects 2026-04-29 Pacific. Every non-core package
  floor on agent-framework-core is raised to >=1.2.2; the new
  contentunderstanding package's stale >=1.0.0 floor is brought into line.
  
  Two follow-on fixes bundled to keep validate-dependency-bounds-test green
  at lowest-direct resolution:
  - Bump agent-framework-azure-contentunderstanding's azure-ai-content
    understanding lower bound from >=1.0.0 to >=1.0.1 (1.0.0 ships without
    proper typing — pyright reports 65 unknown-type errors)
  - Add pyright ignore comments to core/foundry/__init__.pyi for the new
    alpha package's type-stub imports, since alpha packages are not in
    core's [all] extra and therefore aren't installed at lowest-direct
  
  * Python: add #5552 to 1.2.2 CHANGELOG
  
  Add the streaming-span observability fix to the Fixed section. PR is on
  upstream/main but not yet pulled into origin/main; the code itself will
  land via the PR merge.
  
  * Python: address PR #5561 review feedback on dependency bounds
  
  Two packaging fixes flagged in review:
  
  1. agent-framework-azure-contentunderstanding: add agent-framework-foundry
     as a runtime dependency. The package's README directs users to
     `pip install agent-framework-azure-contentunderstanding --pre` and the
     basic example imports `FoundryChatClient` from `agent_framework.foundry`,
     so the documented install path was failing with ImportError. Pulling
     agent-framework-foundry into deps makes the advertised entry path
     self-contained.
  
  2. agent-framework-foundry: bump agent-framework-openai lower bound from
     >=1.1.0 to >=1.2.2,<2. Foundry imports private modules from
     agent_framework_openai (`_chat_client.py:22`, `_agent.py:34`), so
     resolvers were free to pair foundry==1.2.2 with older OpenAI versions
     that lack this release's coordinated Responses/history fix. Lockstep the
     floor with the released cohort to prevent mismatched installs.
  
  Both changes pass `validate-dependency-bounds-test` lower + upper at
  their respective packages.

  Evan Mattson · 2026-04-29 17:51:48 +09:00
  f5419b9f38
• Python: Feature/hosted dwf (#5531)

  * Fix declarative Workflow.as_agent() by accepting list[Message] in start executor
  
  The declarative start executor (JoinExecutor) only advertised dict and str
  in its input_types, so WorkflowAgent.__init__ rejected it with
  'Workflow's start executor cannot handle list[Message]'.
  
  Add list[Message] to the JoinExecutor handler annotation and add a
  matching branch in DeclarativeActionExecutor._ensure_state_initialized
  that extracts the last user-message text and falls through to the
  string-input initialization path, so =System.LastMessageText works
  end-to-end via as_agent().
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Populate Conversation.messages from list[Message] trigger
  
  When Workflow.as_agent() is invoked with a list[Message], the start executor now populates Conversation.messages / Conversation.history / System.conversations.{id}.messages with prior turns only (excluding the latest user message), and surfaces the latest user message via Inputs.input and System.LastMessage*. This matches InvokeAzureAgent's contract that the messages binding holds prior turns and the executor itself appends the new user input before invoking, avoiding double-append of the trailing user turn while preserving full history (incl. assistant/system/tool roles and multi-modal content) for downstream actions.
  
  * Coerce Enum values when serializing PowerFx symbols
  
  MessageRole and other str-subclass Enums passed isinstance(v, str) and were forwarded to pythonnet unchanged. pythonnet then raised 'MessageRole value cannot be converted to System.String' for every PowerFx primitive when ConditionGroup/Expr eval walked the symbol table containing Conversation.messages. Reduce Enum members to their underlying value before the primitive check so eval sees plain strings/ints.
  
  * Foundry hosting: pass full conversation history to workflow agents
  
  _handle_inner_workflow only forwarded the latest user turn to WorkflowAgent.run, even though _handle_inner_agent already prepends history fetched from Foundry storage to the messages it sends a regular agent. Declarative workflows reset Conversation.messages on every run (state.initialize), so checkpoint replay alone does not give them prior turns - the host has to pass them in, the same way it does for non-workflow agents. Mirror that contract: fetch context.get_history() and pass [*history, *input_messages] to the workflow agent.
  
  * feat(workflows): support combined message + checkpoint_id for multi-turn continuation
  
  Allow Workflow.run(message=..., checkpoint_id=...) so callers can restore
  prior workflow state from a checkpoint AND deliver a new message to the
  start executor in a single call. The existing reset_context logic
  already preserves shared state when checkpoint_id is set, so this gives
  us 'fresh start executor invocation with prior state intact' - exactly
  what hosted multi-turn declarative workflows need.
  
  - _workflow.py: drop the message+checkpoint_id mutual exclusion and
    update _execute_with_message_or_checkpoint to do both (restore then
    execute) when both are provided.
  - _agent.py: in _run_core's checkpoint branch, also forward
    input_messages so WorkflowAgent.run(messages, checkpoint_id=...) works
    end-to-end. Falls back to the legacy 'restore only' behavior when
    messages are absent.
  - _declarative_base.py: detect continuation in _ensure_state_initialized
    by checking whether DECLARATIVE_STATE_KEY already exists in shared
    state; if so, refresh inputs/LastMessage* and append non-user trigger
    messages instead of calling state.initialize() (which would wipe
    Conversation/Local/System).
  - foundry_hosting/_responses.py: collapse the host's two-call pattern
    (restore-only, then fresh run) into a single combined call now that
    the underlying APIs support it.
  - tests: drop the assertion that combined message+checkpoint_id raises.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Pivot: preserve workflow state across run() calls
  
  Replace the prior 'combined message + checkpoint_id in one run()' approach
  with a cleaner default: Workflow.run no longer wipes shared state or runner-
  context messages between calls. Iteration counting and per-run kwargs still
  reset on a fresh-message run; checkpoint and responses runs are continuations
  that preserve everything.
  
  This lets a WorkflowAgent be invoked repeatedly on the same instance and
  maintain multi-turn context (e.g. accumulated Conversation.messages) without
  asking developers to opt in. Hosted-agent multi-turn pattern becomes two
  explicit calls: restore-from-checkpoint (drive to idle), then run-with-message.
  
  Key changes:
  - _workflow.py: drop _state.clear() and reset_for_new_run() from run().
    Reset iteration count and run kwargs on fresh-message runs only.
    Restore 'Cannot provide both message and checkpoint_id' validation.
    Add async guard: fresh-message run with un-drained pending executor
    messages from a prior run is invalid.
  - _runner.py: clear _state before import_state in restore_from_checkpoint
    so restore is authoritative (import_state merges, not replaces).
  - _agent.py: revert checkpoint branch to restore-only (no message forward).
  - _responses.py (foundry_hosting): two-call host pattern - restore checkpoint
    silently, then run with new user input.
  - tests: state-preservation is the new default; rebuild Workflow for clean slate.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix CI lint and mypy issues from prior pivot commit
  
  - _workflow.py: collapse nested if (SIM102), drop redundant assignment (RET504)
  - _declarative_base.py: remove unused last_user_msg = tail assignment
    whose Message | None type clashed with the prior Message-typed branch
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address PR review: fix Inputs.input update and checkpoint storage path
  
  - _declarative_base.py: continuation branch was writing 'Inputs.input' via
    state.set, which routes to the Custom namespace and never updates the
    PowerFx-visible Workflow.Inputs.input. Update state_data['Inputs'] in
    place via get_state_data / set_state_data so =Workflow.Inputs.input and
    =inputs.input see the new turn's user text on continuation.
  - _declarative_base.py: refresh docstring to clarify that on a list[Message]
    trigger, Conversation.messages excludes the current user message at the
    start of the turn (agent executors append it before invoking the inner
    agent).
  - _responses.py: when previous_response_id is supplied (no conversation_id),
    the prior checkpoint lives under <storage>/<previous_response_id> but new
    checkpoints must land under <storage>/<current_response_id> for the next
    turn to find them. Hold onto restore_storage from the get_latest lookup
    and pass it to the restore-only run; pass write_storage (current id) to
    the message-delivery run and to checkpoint cleanup.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix pyright errors in _declarative_base.py for CI
  
  - Replace state._state.get(...) protected access with new public
    is_initialized() method on DeclarativeWorkflowState (also clearer intent
    for the continuation detection use case).
  - Add narrow pyright ignores for the Any-typed trigger paths that pyright
    cannot fully narrow (the list[Message] isinstance loop and the
    fallback-DefaultTransform branch).
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address Copilot review batch: tests + Workflow.reset escape hatch
  
  * Add Workflow.reset() public method as recovery escape hatch when an
    in-flight run aborted (e.g. WorkflowConvergenceException) and the
    workflow is not checkpointed. Update the in-flight messages guard's
    error message to point callers at it.
  
  * Add test_workflow_run_inflight_messages_guard exercising both the
    guard (sync + streaming) and the reset() recovery path.
  * Add test_workflow_reset_rejects_concurrent_runs to lock down the
    in-progress guard on reset.
  
  * Add test_as_agent_continuation_preserves_prior_state covering the
    is_continuation branch in _ensure_state_initialized: stamps a marker
    between calls and asserts it survives, while Inputs.input and
    System.LastMessageText refresh to the new turn.
  
  * Add test_powerfx_safe.py regression tests for the Enum branch in
    _make_powerfx_safe (str-subclass, int-subclass, plain Enum, and
    Enums nested in dict/list).
  
  * Drop redundant @pytest.mark.asyncio on
    test_as_agent_round_trip_with_last_message_text (asyncio_mode='auto').
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Skip restore-only pre-pass when checkpoint has pending request_info
  
  Address Copilot review on _responses.py: the restore-only checkpoint
  replay populates self._agent.pending_requests for any request_info
  events captured in the checkpoint. The follow-up run(input_messages)
  call would then route through WorkflowAgent._process_pending_requests,
  which expects function-response content and rejects plain text input
  as 'unexpected content while awaiting request info responses'.
  
  Workflows resumed from a checkpoint that was idle-with-pending-requests
  would therefore fail every subsequent plain-text user turn. Inspect the
  loaded checkpoint and skip the pre-pass when its
  pending_request_info_events dict is non-empty. Workflows that don't use
  request_info (the current sample set) are unaffected; workflows that do
  will fall through to a fresh-message run rather than silently corrupting
  the routing state.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Loosen azure-ai-agentserver-* pins to major version
  
  The exact-version pins on azure-ai-agentserver-{core,responses,invocations}
  forced foundry-hosting consumers to upgrade in lockstep with every beta
  bump from upstream. Switch to '>=current,<next-major' so we pick up patch
  and feature updates within the same major series without a coordinated
  release.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Drop Workflow.reset(); checkpointing is the recovery path
  
  The in-flight-messages guard prevented silent misbehavior, but the
  companion Workflow.reset() escape hatch only cleared _messages while
  leaving iteration count, executor-local state, and shared State
  mutations in an indeterminate condition after a mid-run failure. That
  gave a false sense of recovery.
  
  Recovery from a mid-run failure is supported only via checkpoint
  restoration. Keep the guard and reframe its error message accordingly;
  remove reset() and its tests.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address Tao's review on PR 5531
  
  - Rename Workflow._run_workflow_with_tracing parameter
    is_fresh_message_run -> is_continuation (default False, inverted).
    Fresh-message turns reset per-run accounting; continuations
    (checkpoint restores, responses replays) preserve it.
  - Simplify the in-flight-messages guard: _validate_run_params already
    enforces that 'message' is mutually exclusive with 'checkpoint_id'
    and 'responses', so the additional checks were dead code.
  - foundry_hosting _responses: move the restore-only pre-pass above
    emit_created/emit_in_progress; restore is preparation, not run
    progress. Drop the skip-restore gate (state preservation requires
    unconditional restore) and instead clear agent.pending_requests
    after the restore-only call. Collapse over-conditioned check.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Don't clear pending_requests after restore-only pre-pass
  
  Pending requests in the restored checkpoint represent genuinely
  outstanding HITL requests. The next user input may carry function
  responses (Responses API `function_call_output` items become
  FunctionResultContent / FunctionApprovalResponseContent), which
  `WorkflowAgent._process_pending_requests` correctly extracts and
  matches against the populated `pending_requests`. Clearing them
  after restore would silently drop that state and force the next turn
  to be treated as a fresh input even when the caller is responding to
  the outstanding requests.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: alliscode <bentho@microsoft.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  Co-authored-by: Evan Mattson <35585003+moonbox3@users.noreply.github.com>

  Ben Thomas · 2026-04-29 00:51:49 +00:00
  8b71f9459a
• Python: [BREAKING] Standardize orchestration terminal outputs as AgentResponse (#5301)

  * Fix orchestration outputs so as_agent() returns the final answer only. Align other orchestration outputs
  
  * Fix orchestration output issues from review comments
  
  1. Sample cleanup: Remove commented-out FoundryChatClient block and update
     prerequisites to reference OPENAI_CHAT_MODEL_ID instead of FOUNDRY_* vars.
  
  2. Sequential approval output: Change _EndWithConversation.end_with_agent_executor_response
     from a no-op sink to yield response.agent_response. When the last participant is
     AgentApprovalExecutor (via with_request_info), _EndWithConversation is the output
     executor so the yield produces the terminal answer. When the last participant is a
     regular AgentExecutor, _EndWithConversation is not in output_executors so the yield
     is silently filtered out.
  
  3. Forward data events through WorkflowExecutor: _process_workflow_result now also
     forwards 'data' events from sub-workflows so that emit_intermediate_data=True on
     AgentExecutor works correctly when wrapped in AgentApprovalExecutor.
  
  4. Concurrent docstring: Update _AggregateAgentConversations docstring to say
     'deterministic participant order' instead of 'completion order'.
  
  5. Add test_concurrent_intermediate_outputs_emits_data_events verifying that
     ConcurrentBuilder(intermediate_outputs=True) emits per-participant data events
     alongside the single aggregated output event.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Add tests for sequential workflow with_request_info and intermediate_outputs (#5301)
  
  Address PR review comments 2, 3, and 5:
  
  - Add test_sequential_request_info_last_participant_emits_output:
    Verifies that when the last participant is wrapped via with_request_info()
    (AgentApprovalExecutor), the workflow still emits a terminal output after
    approval, exercising the _EndWithConversation.end_with_agent_executor_response
    fallback path.
  
  - Add test_sequential_request_info_with_intermediate_outputs_emits_data_events:
    Verifies that emit_intermediate_data=True works correctly through
    AgentApprovalExecutor wrapping—WorkflowExecutor._process_result already
    forwards data events from sub-workflows, so intermediate agent responses
    surface as data events in the parent workflow.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix pyright type errors from AgentResponse output refactor (#5301)
  
  Update cast() calls in _group_chat.py and _magentic.py to use
  WorkflowContext[Never, AgentResponse] instead of the old
  WorkflowContext[Never, list[Message]], matching the updated method
  signatures in _base_group_chat_orchestrator.py.
  
  Fix _sequential.py _EndWithConversation.end_with_agent_executor_response
  to declare WorkflowContext[Any, AgentResponse] so yield_output accepts
  AgentResponse[None].
  
  Fix _workflow_executor.py data event forwarding to handle nullable
  executor_id.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix pyright reportUnknownVariableType in _agent.py (#5301)
  
  Extract event.data into a typed local variable before the isinstance
  check to avoid pyright narrowing it to AgentResponse[Unknown].
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix pyright reportMissingImports for orjson in file history samples (#5301)
  
  Add pyright: ignore[reportMissingImports] to orjson imports that are
  already guarded by try/except ImportError, matching the existing pattern
  used elsewhere in the samples.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address review feedback for #5301: review comment fixes
  
  * Address review feedback for #5301: review comment fixes
  
  * Revert sequential_workflow_as_agent sample to FoundryChatClient
  
  Reverts the mistaken switch from FoundryChatClient to OpenAIChatClient
  in the sequential workflow as agent sample.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address ultrareview feedback: emit_data_events rename + WorkflowAgent reasoning conversion
  
  Layered on top of the prior review-feedback work in this branch.
  
  Renames:
  - AgentExecutor.emit_intermediate_data -> emit_data_events (mechanical
    rename; orchestration semantics live at the orchestration layer, not
    the general-purpose executor). Forwarded through MagenticAgentExecutor,
    AgentApprovalExecutor, and all orchestration call sites.
  - HandoffAgentExecutor._check_terminate_and_yield -> _should_terminate
    (pure predicate; no longer yields anything). HandoffBuilder docstring
    rewritten to describe the new per-agent AgentResponse output contract.
  
  WorkflowAgent reasoning-content conversion:
  - Add _rewrite_text_to_reasoning(contents) and _msg_as_reasoning(msg)
    helpers; the as_agent() path now reframes text content from data events
    as text_reasoning Content blocks before merging into the AgentResponse.
  - Consumers iterate msg.contents and branch on content.type — same path
    they already use for Claude thinking and OpenAI reasoning. No new
    field on Message/AgentResponse/WorkflowEvent.
  - Streaming branch constructs fresh AgentResponseUpdate instances instead
    of mutating shared payloads (regression test added).
  - Helper _msg_maybe_reasoning consolidates the conditional rewrite at
    three call sites in the non-streaming conversion.
  
  Tests:
  - TestWorkflowAgentReasoningHelpers + TestWorkflowAgentDataEventReasoningConversion
    add 9 new tests covering helpers, non-streaming, streaming, mixed content,
    already-reasoning passthrough, and mutation-safety regression.
  - Updated test_sequential_as_agent_with_intermediate_outputs_includes_chain
    to assert text_reasoning content for intermediate agents.
  
  * Fix pyright: widen event.data to Any to avoid partial-unknown narrowing
  
  The streaming conversion path narrowed event.data via isinstance against
  generic AgentResponse, producing AgentResponse[Unknown] and tripping
  reportUnknownVariableType/reportUnknownMemberType. Binding data: Any
  before the check keeps runtime behavior identical while restoring a fully
  known type for downstream access.
  
  * Clean up design
  
  * Scope to agent output semantics only
  
  * yield AgentResponseUpdate streaming, AgentResponse non-streaming
  
  * Fix mypy/pyright: widen cast types at GroupChat callsites
  
  Eight callsites in _group_chat.py still cast to WorkflowContext[Never,
  AgentResponse] but the base orchestrator methods now accept the wider
  WorkflowContext[Never, AgentResponse | AgentResponseUpdate] (mode-aware
  yields). W_OutT is invariant, so the narrower cast is not assignable.
  Magentic was widened in the same commit; this catches the GroupChat
  callsites that were missed.
  
  * Python: skip flaky Foundry / Foundry Hosting integration tests (#5553)
  
  These two integration tests have been failing in the merge queue across
  multiple unrelated PRs (5301, 5531). Both are marked `@pytest.mark.flaky`
  with 3 retries, but all attempts fail back-to-back. Skipping both with a
  reason pointing to #5553 so they can be fixed properly without continuing
  to block unrelated merges.
  
  - packages/foundry_hosting/tests/test_responses_int.py::TestOptions::test_temperature_and_max_tokens
  - packages/foundry/tests/foundry/test_foundry_embedding_client.py::TestFoundryEmbeddingIntegration::test_text_embedding_live
  
  Also includes a one-line uv.lock specifier-ordering normalization
  auto-applied by the poe-check pre-commit hook.
  
  ---------
  
  Co-authored-by: Copilot <copilot@github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Evan Mattson · 2026-04-29 00:35:36 +00:00
  866a325b48
• Python: bump package versions for 1.2.1 release (#5536)

  * Python: bump package versions for 1.2.1 release
  
  PATCH bump (1.2.0 -> 1.2.1) for the released cohort. The release window
  covers two PRs, no new public APIs:
  
  - agent-framework-core: prevent inner_exception from being lost in
    AgentFrameworkException (#5167)
  - samples: add requirements.txt and .env.example to the a2a/ hosting
    sample for pip-based setup (#5510)
  
  Per lockstep convention, all 21 beta packages stamp 1.0.0b260428 and all
  3 alpha packages stamp 1.0.0a260428, regardless of per-package code
  churn. Every non-core package floor on agent-framework-core is raised to
  >=1.2.1 to keep cohort signaling consistent. Date stamp reflects the
  local (Asia) cut date 2026-04-28.
  
  * Python: silence pyright unknown-type warnings in hosted-env detection
  
  `azure.ai.agentserver.core` is probed at runtime via `importlib.util.find_spec`
  and is not a declared dependency. The existing `# pyright: ignore[reportMissingImports]`
  suppresses the missing-import warning, but at `lowest-direct` resolution pyright
  still reports the imported symbol (`AgentConfig`) and its members (`from_env`,
  `is_hosted`) as unknown, breaking `validate-dependency-bounds-test` for
  `packages/core`.
  
  Extend the existing ignore to cover `reportUnknownVariableType` on the import
  and `reportUnknownMemberType` on the call site so the bounds check returns to
  green. Behavior is unchanged.
  
  Latent since #5455 (shipped in 1.2.0).
  
  * Python: raise agent-framework-gemini lower bound to google-genai>=1.65.0
  
  The Gemini chat client references several `google.genai.types` symbols
  (`FileSearch`, `ThinkingLevel`, `SearchTypes`, `McpServer`,
  `StreamableHttpTransport`, plus call-site keyword args `mcp_servers` and
  `search_types`) that are not present at the lower bound of `google-genai>=1.0.0`.
  At `lowest-direct` resolution this caused `validate-dependency-bounds-test` to
  fail for `packages/gemini` with eleven `reportAttributeAccessIssue` /
  `reportUnknownVariableType` errors.
  
  Walking the upstream `google.genai.types` API:
  - `GoogleMaps`, `AuthConfig`: present from 1.40.0
  - `FileSearch`: introduced in 1.49.0
  - `ThinkingLevel`: introduced in 1.55.0
  - `SearchTypes`, `McpServer`, `StreamableHttpTransport`: introduced in 1.65.0
  
  Bump the lower bound to 1.65.0 — the minimum version that exposes every symbol
  the package actually uses. Keep the `<2.0.0` upper cap unchanged. With this
  bump `validate-dependency-bounds-test` passes for both lower and upper
  resolution scenarios across all 27 workspace packages.
  
  Latent since #4847 (Gemini package introduction in 1.1.0); aggravated by
  subsequent feature additions that pulled in newer `types.*` symbols.
  
  * Python: add dependabot bumps to 1.2.1 CHANGELOG
  
  Catalog the 15 dependabot dependency updates that merged on `upstream/main`
  between python-1.2.0 and the 1.2.1 cut window under a new Changed section:
  
  - Workspace dev/runtime deps: `rich`, `prek`, `python-multipart`, `pyasn1`,
    `pytest` (ag-ui, devui, lab), `uv` (lab)
  - Frontend deps: `vite` (devui, chatkit), `postcss` (devui, chatkit, handoff),
    `picomatch` (devui, handoff)
  
  CHANGELOG-only — no source or pyproject.toml changes. PRs themselves merged
  upstream independently of this release branch and will be brought in via the
  PR merge.

  Evan Mattson · 2026-04-28 18:23:26 +09:00
  3a463b8bf6
• Python: Update hosting agent samples + fixes (#5485)

  * Update foundry hosting samples
  
  * Add file data type support
  
  * Fix file content and add more tests
  
  * Fix README
  
  * Address comments
  
  * Fix int tests
  
  * remove temp

  Tao Chen · 2026-04-28 04:24:05 +00:00
  88347f6494
• Python: Bump Python package versions for 1.2.0 release (#5468)

  * Bump Python package versions for 1.2.0 release
  
  Released tier bumps 1.1.1 -> 1.2.0 (core, openai, foundry, root) to
  reflect additive public APIs landed since 1.1.0: functional workflow API
  (#4238) and FunctionTool SKIP_PARSING sentinel (#5424). All beta packages
  stamped 1.0.0b260424, alpha packages 1.0.0a260424. All 26 non-core
  agent-framework-core floors raised to >=1.2.0,<2. CHANGELOG consolidates
  the never-tagged 1.1.1 entries with the post-merge additions into [1.2.0].
  
  * Update CHANGELOG footer links for 1.2.0
  
  Advance [Unreleased] comparison base from python-1.1.0 to python-1.2.0
  and add a [1.2.0] reference link comparing python-1.1.0...python-1.2.0
  so the heading links resolve correctly.
  
  * Fix CHANGELOG: restore [1.1.1] section and add proper [1.2.0]
  
  Previous commit incorrectly renamed the [1.1.1] header to [1.2.0], which
  wiped the historical 1.1.1 entries and wrongly attributed them to 1.2.0.
  This restores [1.1.1] to its origin/main content and adds a new [1.2.0]
  section above containing only the commits in python-1.1.1..HEAD:
  
  - #4238 functional workflow API
  - #5142 GitHub Copilot OpenTelemetry
  - #2403 A2A bridge support
  - #5070 oauth_consent_request events in Foundry clients
  - #5447 FoundryAgent hosted agent sessions
  - #5459 hosting server dependency upgrade + types
  - #5389 AG-UI reasoning/multimodal parsing fix
  - #5440 stop [TOOLBOXES] warning spam
  - #5455 user agent prefix fix
  
  Also corrects the [1.2.0] compare base to python-1.1.1 (not 1.1.0) and
  adds the missing [1.1.1] reference link.

  Evan Mattson · 2026-04-24 19:54:59 +09:00
  0b69d7fd15
• Python: update FoundryAgent for hosted agent sessions (#5447)

  * fixes to FoundryAgent to connect to new hosted agents
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * fix mypy
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * Python: remove Foundry service session helpers
  
  Remove the public hosted-agent service session CRUD helpers from FoundryAgent and drop the related feature-stage inventory entry.
  
  Update the hosted-agent sample to create and delete service sessions directly through the preview AIProjectClient APIs, and tighten a few test harnesses surfaced by full workspace validation.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix from merge
  
  * fix hosted env detection
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * reverted sample update
  
  * fix tests and code
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * remove aenter
  
  * skipping some tests
  
  Co-authored-by: Copilot <copilot@github.com>
  
  ---------
  
  Co-authored-by: Copilot <copilot@github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-04-24 09:25:03 +00:00
  62e02da698
• Python: Upgrade hosting server dependency and add more type support (#5459)

  * Upgrade hosting server dependency and add more type support
  
  * Comments

  Tao Chen · 2026-04-24 07:27:17 +00:00
  4adfd244ac
• Python: Fix user agent prefix (#5455)

  * Fix hosting user agent missing
  
  * Fix other providers
  
  * Add more tests
  
  * comments
  
  * Fix tests

  Tao Chen · 2026-04-23 23:40:38 +00:00
  0989e68d1c
• Python: Bump Python package versions for a release. (#5432)

  * Bump Python version for a release.
  
  * Revert lockstep bumps on unchanged connectors
  
  Per PR review: only connectors that changed (or whose published metadata
  changed) should get new versions. Keeps released tier at 1.1.1, a2a/ag-ui
  at 1.0.0b260422, foundry-hosting at 1.0.0a260422; reverts the 19 unchanged
  betas and 2 unchanged alphas to 1.0.0b260421/1.0.0a260421. Reverts all 26
  non-core agent-framework-core floors to >=1.1.0,<2 since no connector
  actually depends on a 1.1.1 API or bug fix.
  
  * Restore lockstep prerelease bumps and raise core floors to >=1.1.1
  
  Reverses the lean-revert: all beta packages stamped 1.0.0b260423 and alpha
  packages stamped 1.0.0a260423 (Asia date, matching release cut time). All
  26 non-core packages raise agent-framework-core lower bound from >=1.1.0,<2
  to >=1.1.1,<2 to signal the validated cohort for this release. CHANGELOG
  date updated to 2026-04-23.

  Evan Mattson · 2026-04-23 16:40:14 +09:00
  acec9caa2f
• Adjust dev status for alpha from 4 to 3 in foundry hosting pyproject.toml (#5387)
  Evan Mattson · 2026-04-22 17:48:02 +00:00
  d75f874d78
• Python: Bump versions for a release. Update CHANGELOG (#5385)

  * Bump versions for a release. Update CHANGELOG
  
  * Bump devui

  Evan Mattson · 2026-04-21 15:14:42 +09:00
  2c8036779c
• Python: Foundry hosted agent V2 (#5379)

  * Python: Wrapper + Samples 1st (#5177)
  
  * Experiment
  
  * Update dependency and add non streaming
  
  * Add more samples
  
  * Rename samples
  
  * Add invocations
  
  * Comments 1
  
  * Comments 2
  
  * Comments 3
  
  * Improve README
  
  * Add local shell sample
  
  * WIP: Add eval and memory samples
  
  * Update user agent prefix
  
  * Update user agent prefix doc
  
  * Update dependency (#5215)
  
  * Add tests and more content types (#5235)
  
  * Add tests
  
  * fix tests and sample
  
  * Fix formatting
  
  * Remove function approval contents
  
  * Python: Refine samples and upgrade packages (#5261)
  
  * Refine samples and upgrade pacakges
  
  * Upgrade to a new package that fixes a bug
  
  * Update model env var
  
  * Move samples (#5281)
  
  * Python: Upgrade agentserver packages (#5284)
  
  * Upgrade agentserver packages
  
  * Fix new types
  
  * Python: Add special handling for workflows (#5298)
  
  * Add special handling for workflows
  
  * Address comments
  
  * Improve samples (#5372)
  
  * Python: Add more types (#5378)
  
  * Add more type supports
  
  * Upgrade packages
  
  * Remove TODOs in README
  
  * Fix README
  
  * Comments and mypy
  
  * User agent scoped
  
  * Fix README
  
  * Fix pre commit
  
  * Fix pre commit 2
  
  * Fix pre commit 3
  
  * Fix pre commit 4
  
  * Fix pre commit 5
  
  * Fix pre commit 6
  
  * Add azure-monitor-opentelemetry to dev deps
  
  Fixes Samples & Markdown CI failure. The PR's new transitive dep on
  azure-monitor-opentelemetry-exporter (via azure-ai-agentserver-core) makes
  pyright resolve the azure.monitor.opentelemetry namespace, flipping the
  check_md_code_blocks diagnostic for `configure_azure_monitor` from
  reportMissingImports (filtered) to reportAttributeAccessIssue (not filtered).
  Installing the umbrella azure-monitor-opentelemetry package in dev makes
  pyright resolve the symbol correctly, matching the install guidance the
  observability README already gives users.
  
  ---------
  
  Co-authored-by: Evan Mattson <evan.mattson@microsoft.com>

  Tao Chen · 2026-04-21 05:21:27 +00:00
  ce8b6305d8