Skip to content

Publish the command as ChromaDotNet.Client.Cli - #168

Merged
Laurianti merged 2 commits into
mainfrom
tool-rename
Nov 15, 2026
Merged

Laurianti merged 2 commits into
mainfrom
tool-rename

Conversation

@Laurianti

@Laurianti Laurianti commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

The package of the chromadotnet command is now ChromaDotNet.Client.Cli instead of ChromaDotNet.Tool, so that it matches the ChromaDotNet.Client* pattern of the Trusted Publishing policy on nuget.org, like the other packages. The command name does not change, and ChromaDotNet.Tool was never published.

  • The project, its folder and its namespace are now ChromaDB.Client.Cli, like ChromaDB.Client.Backup; the package is ChromaDB.Client.Cli without a prefix.
  • ci.yml, release-assets.yml, README.md, docs/backup.md and the tests: the new names.

Tested: the package packed with the prefix, installed from a local source, and backup, verify and restore run against Chroma 1.5.9.

The ID matches the pattern ChromaDotNet.Client* of the Trusted Publishing policy on nuget.org. The command stays chromadotnet; the package was never published.
@Laurianti
Laurianti requested a review from a team as a code owner November 15, 2026 15:31
The package, the project, its folder, the namespace and the tests say Cli instead of Tool. The command stays chromadotnet.
@Laurianti Laurianti changed the title Publish the command as ChromaDotNet.Client.Tool Publish the command as ChromaDotNet.Client.Cli Nov 15, 2026
@Laurianti
Laurianti merged commit d7de48a into main Nov 15, 2026
23 checks passed
@Laurianti
Laurianti deleted the tool-rename branch November 15, 2026 15:47
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