[github-actions]

This pull request updates CODEOWNERS for a new integration submission.

• Source PR: Add Chroma hosting and client integrations #2219
• Proposed code owner: @Laurianti
• Package IDs:
• CommunityToolkit.Aspire.Chroma
• CommunityToolkit.Aspire.Hosting.Chroma

[aaronpowell]

@Laurianti Are you able to be the long-term CODEOWNER for the Chroma integrations?

[Laurianti]

Yes, I can. I'll keep the Chroma integrations in step with new Aspire and Chroma releases. Thanks for merging #2246 too.

[aaronpowell]

Sent you an invite to join the GitHub team, once that's merged the CODEOWNERS will be valid and I'll merge this

[Laurianti]

Joined, thanks Aaron!

[Laurianti]

@aaronpowell the build of 13 October pushed CommunityToolkit.Aspire.Chroma and CommunityToolkit.Aspire.Hosting.Chroma 13.6.1-beta.933, and nuget.org accepted them, but the two packages are still not on nuget.org. CommunityToolkit.VectorData.Chroma had the same wait on 9 October, until the .NET Foundation approved the co-ownership of the new package. Could the Chroma ones be waiting for the same?

[afscrome]

@Laurianti Looks like the Chroma package was added after hte latest release - https://github.com/CommunityToolkit/Aspire/releases/tag/v13.6.0 .

Next release will presumably be 17.0 alongside Aspire 17.0.

[Laurianti]

@afscrome thanks. The other integrations have 13.6.1-beta.933 on nuget.org from the same build (for example CommunityToolkit.Aspire.Hosting.Adminer), while the two Chroma packages don't. Since they are new package IDs, could they be waiting for the .NET Foundation approval?