Expanding list of CODEOWNERS for registry.json to include Foundry developers.

[richardpark-msft]

Welcome new developers to registry.json :) (once this PR merges!)

The basics of how this'll work for you, with regards to registry PRs:

• If it's just a simple registry update (new version for an existing extension, no provider or capability updates) then you, or anyone else in CODEOWNERS can just approve and merge the PR.

• If it's a complex one (ie, any of those things change), you'll see this PR workflow fail:

  

  If you click it (link) it'll tell you the specific item that's requires approval. So then:

  1. Contact an azd core team member, and provided it's "okay" (@tg-msft is working on docs) then they'll approve it and the release can happen.
  2. Re-run that failed step and it'll evaluate and will pass.

Fixes #8997

[azure-pipelines]

Azure Pipelines:
22 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
22 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Expands registry ownership so Foundry developers can approve routine extension publishing updates.

Changes:

• Adds Foundry developers as code owners for registry.json.
• Retains core-review enforcement for complex registry changes.

Show a summary per file

File	Description
.github/CODEOWNERS	Expands ownership of the extension registry.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Medium

[github-actions]

📋 Prioritization Note

Thanks for the contribution! The linked issue isn't in the current milestone yet.
Thank you for logging this issue; our team is reviewing it. If you need urgent prioritization, tag @RickWinter and @kristenwomack to let us know.

[richardpark-msft]

/check-enforcer evaluate

[richardpark-msft]

/check-enforcer override

[richardpark-msft]

CC: @XiaofuHuang @achauhan-scc @anchenyi @glharper @huimiu @hund030 @kingernupur @saanikaguptamicrosoft @therealjohn @trangevi @trrwilson

Okay NOW you can approve extension release PRs, sorry about that false alarm earlier. :) Check the PR message for instructions, but it should be pretty much like any ole' PR for most situations.