Skip to content
This repository was archived by the owner on Nov 5, 2026. It is now read-only.

Say that the client package connects to Chroma Cloud, and tag it chroma and chroma-cloud - #1

Merged
Laurianti merged 1 commit into
mainfrom
package-cloud-tags
Oct 5, 2026
Merged

Laurianti merged 1 commit into
mainfrom
package-cloud-tags

Conversation

@Laurianti

Copy link
Copy Markdown
Member

The NuGet description of ChromaDotNet.Aspire.Client says that it connects to a Chroma server or to Chroma Cloud, and its tags add chroma and chroma-cloud. Only the part that this repository adds changes, so the project folders stay identical to CommunityToolkit/Aspire#2219. ChromaDotNet.Aspire.Hosting runs a Chroma container, and keeps its description and tags.

Copilot AI balanced review requested due to automatic review settings October 5, 2026 09:25

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

The targeted metadata changes correctly match the stated package roles.

Review effort: Balanced
Findings: None

What changed in this PR

Updates NuGet metadata so the client package advertises Chroma Cloud support while leaving hosting metadata unchanged.

Changes:

  • Adds a client-specific package description.
  • Adds chroma and chroma-cloud client tags.
  • Extracts the shared package disclaimer.
File Description
src/​Directory.Build.targets Defines shared and client-specific NuGet metadata.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@Laurianti
Laurianti merged commit 4c460e3 into main Oct 5, 2026
4 checks passed
@Laurianti
Laurianti deleted the package-cloud-tags branch October 5, 2026 09:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants