Skip to content

Add CODEOWNERS entry for integration PR #2219 - #2245

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
automation/codeowners-pr-2219
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
automation/codeowners-pr-2219

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This pull request updates CODEOWNERS for a new integration submission.

@github-actions github-actions Bot mentioned this pull request Oct 12, 2026
9 of 10 tasks
@aaronpowell

Copy link
Copy Markdown
Member

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

@Laurianti

Copy link
Copy Markdown
Member

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

@aaronpowell

Copy link
Copy Markdown
Member

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

@Laurianti

Copy link
Copy Markdown
Member

Joined, thanks Aaron!

@Laurianti

Copy link
Copy Markdown
Member

@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?

This branch has not been deployed

No deployments
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