Skip to content

[Agents Extension] Registry update#8002

Merged
trangevi merged 2 commits into
mainfrom
releases/azure.ai.agents-0.1.29-preview
Apr 30, 2026
Merged

[Agents Extension] Registry update#8002
trangevi merged 2 commits into
mainfrom
releases/azure.ai.agents-0.1.29-preview

Conversation

@trangevi

@trangevi trangevi commented Apr 30, 2026

Copy link
Copy Markdown
Member

Fixes #8001

Signed-off-by: trangevi <trangevi@microsoft.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the AZD extensions registry to publish a new Azure AI Agents extension release and adjust the registry metadata.

Changes:

  • Adds azure-ai-agents extension version 0.1.29-preview with updated artifacts and checksums.
  • Removes the top-level schemaVersion field from the registry JSON.

Comment thread cli/azd/extensions/registry.json
Comment thread cli/azd/extensions/registry.json

@jongio jongio left a comment

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.

Verified the 0.1.29-preview registry entry:

  • Release artifacts exist at the expected URLs
  • Checksum verified (spot-checked windows/amd64 - matches)
  • JSON validates cleanly
  • Structure and capabilities match the previous 0.1.27/0.1.28 entries
  • The schemaVersion removal is fine since the Registry struct doesn't parse it

LGTM.

@wbreza wbreza left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Review Summary

TL;DR: The new �.1.29-preview version entry looks correct and well-formed. One question about an unrelated change bundled in.

⚠️ schemaVersion removal — intentional?

This PR removes the "schemaVersion": "1.0" field from the top of
egistry.json. This field was deliberately added in PR #7837 (merged 2 days ago) along with validation code in
egistry_version.go (CheckRegistrySchemaVersion()) to support future registry schema evolution.

The backward-compat logic treats a missing schemaVersion as "1.0", so nothing breaks — but this silently undoes the foundation for schema versioning.

Was this removal intentional? If so, should it be discussed separately from the registry update? If not, it may just need to be reverted (keep the schemaVersion line).

💬 Minor: PR description typo

The description reads Fixes #8001 8001 — the issue number appears duplicated.

✅ New version entry

The �.1.29-preview block looks good — all 6 platform artifacts, SHA256 checksums, consistent URL patterns and archive formats.

@github-actions

github-actions Bot commented Apr 30, 2026

Copy link
Copy Markdown

📋 Prioritization Note

Thanks for the contribution! The linked issue isn't in the current milestone yet.
Review may take a bit longer — reach out to @rajeshkamal5050 or @kristenwomack if you'd like to discuss prioritization.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@trangevi
trangevi enabled auto-merge (squash) April 30, 2026 23:14
@trangevi

Copy link
Copy Markdown
Member Author

/check-enforcer override

@trangevi
trangevi merged commit e32b523 into main Apr 30, 2026
4 checks passed
Copilot AI pushed a commit that referenced this pull request May 21, 2026
* registry update

Signed-off-by: trangevi <trangevi@microsoft.com>

* Update cli/azd/extensions/registry.json

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

---------

Signed-off-by: trangevi <trangevi@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: therealjohn <1501196+therealjohn@users.noreply.github.com>
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.

Update registry for agents extension

5 participants