CI test failures on main: codeowners-linter (invalid user `@ZachhK` in CODEOWNERS)

[github-actions]

Summary

1 CI pipeline check is failing on the main branch at commit 802e8ced (2026-05-15). The js - codeowners-linter - ci check run is failing due to @ZachhK being listed as an owner in .github/CODEOWNERS for the ai-agents and ai-projects service directories — this user is flagged as invalid (does not exist, is not a public member of Azure org, or lacks write permissions).

All other failing check runs on this commit are CI infrastructure failures (Windows test-proxy not found, npm authentication failures with exit code 57005, manifest generation failures), not code regressions.

Failures

CODEOWNERS Linter (js - codeowners-linter - ci)

Failing check: js - codeowners-linter - ci (check run 76402486790)

Failing lines in .github/CODEOWNERS:

• Line 39: /sdk/ai/ai-agents @bobogogo1990 @dargilco @ganeshyb @glharper @ZachhK``
• Line 42: # ServiceOwners: @bobogogo1990 @dargilco @ganeshyb @glharper @ZachhK``
• Line 51: /sdk/ai/ai-projects @bobogogo1990 @dargilco @ganeshyb @glharper @ZachhK``
• Line 54: # ServiceOwners: @bobogogo1990 @dargilco @ganeshyb @glharper @ZachhK``

Error:

.github/CODEOWNERS(39,1): error : Error(s) on line 39
Source Line: /sdk/ai/ai-agents    `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper` `@ZachhK`
  -ZachhK is an invalid user. Ensure the user exists, is public member of Azure and has write permissions.

.github/CODEOWNERS(42,1): error : Error(s) on line 42
Source Line: # ServiceOwners: `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper` `@ZachhK`
  -ZachhK is an invalid user. Ensure the user exists, is public member of Azure and has write permissions.

.github/CODEOWNERS(51,1): error : Error(s) on line 51
Source Line: /sdk/ai/ai-projects    `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper` `@ZachhK`
  -ZachhK is an invalid user. Ensure the user exists, is public member of Azure and has write permissions.

Root cause:
@ZachhK is referenced as a code owner for sdk/ai/ai-agents and sdk/ai/ai-projects but is no longer a valid user (either the account was removed, made private, or had its repository write permissions revoked).

Suggested fix:

Remove @ZachhK from all four lines in .github/CODEOWNERS:

--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -36,14 +36,14 @@
 # PRLabel: %AI Agents
-/sdk/ai/ai-agents    `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper` `@ZachhK`
+/sdk/ai/ai-agents    `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper`
 
 # ServiceLabel: %AI Agents
-# ServiceOwners: `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper` `@ZachhK`
+# ServiceOwners: `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper`
 
 # PRLabel: %AI Projects
-/sdk/ai/ai-projects    `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper` `@ZachhK`
+/sdk/ai/ai-projects    `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper`
 
 # ServiceLabel: %AI Projects
-# ServiceOwners: `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper` `@ZachhK`
+# ServiceOwners: `@bobogogo1990` `@dargilco` `@ganeshyb` `@glharper`

Alternatively, if @ZachhK should be replaced by another user, update the entries accordingly.

Reproduced locally: N/A (CODEOWNERS linter runs in CI only)

---

Additional Notes

All other failing CI check runs on commit 802e8ced are infrastructure failures unrelated to source code:

• Windows test-proxy not found (D:\a\_work\1\a\test-proxy.log missing): affects databox-mgmt, service-map-mgmt, securitydevops-mgmt unit test jobs.
• npm authentication failure (exit code 57005 / npmAuthenticate task): affects computelimit-mgmt, confluent-mgmt, agrifood-mgmt, lambdatesthyperexecute-mgmt.
• Bash exit code 255 (Azure Key Vault / auth): affects apimanagement (all platforms).
• Manifest generation / packages-dev-publish path missing: affects databox-mgmt, storage, batch, eventhub-mgmt, contentunderstanding, applicationinsights-mgmt, analysisservices-mgmt build jobs.
• PublishDocsToNightlyBranch integration failures: affects many packages but these are doc-publishing tasks, not test failures.

These infrastructure failures are not caused by code changes in this repository and should be investigated by the CI infrastructure team.

No failures matched the known pre-existing failures tracked in #37864 (which currently has no entries).

Generated by Analyze CI Test Failures · ● 1.1M · ◷