Skip to content

[ai-projects] Regenerate from azure-rest-api-specs@16c414e#39237

Draft
glharper wants to merge 6 commits into
mainfrom
regen/ai-projects/16c414e-20260710
Draft

[ai-projects] Regenerate from azure-rest-api-specs@16c414e#39237
glharper wants to merge 6 commits into
mainfrom
regen/ai-projects/16c414e-20260710

Conversation

@glharper

@glharper glharper commented Jul 10, 2026

Copy link
Copy Markdown
Member

Description

Regenerates @azure/ai-projects from Azure/azure-rest-api-specs@16c414e.

  • Refreshes emitted client code after the upstream Foundry/OpenAI route-directory reorganization and updates the corresponding TypeSpec input paths.
  • Adds the GA project.agents.patchAgentObject method and AgentsPatchAgentObjectOptionalParams alias while retaining the existing updateAgent compatibility surface.
  • Updates the hosted-agent image sample to demonstrate patchAgentObject and adds a skipped, recorder-ready GA test.
  • Adds a 2.4.0 (Unreleased) changelog entry and synchronizes the package version.
  • Expands the post-emitter skill with recovery guidance learned during this regeneration, including protected-path normalization, conflict-corrupted model recovery, and interrupted dependency-install handling.

Verification

  • npx dev-tool run build-package (browser, React Native, ESM, and CommonJS)
  • npm run check-format
  • npm run build:samples
  • tsc -p tsconfig.test.node.json --noEmit
  • New skipped test passes ESLint and editor diagnostics
  • review/ai-projects-node.api.md reviewed; API diff is additive
  • npm run test:node completes without live-service failures
    • The new patchAgentObject test is intentionally skipped pending a recording.
    • Existing live tests reached the service but failed with unrelated 403 authorization errors for the current identity.

downloadAgentCode,
createVersionFromCode,
updateAgentObject,
patchAgentObject,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need rename patch to update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants