Repository navigation
fix(npm): publish the launcher as @kerrshift/agentdiff - #64
Merged
Merged
Conversation
npm rejects the unscoped name agentdiff as too similar to the existing agent-diff package, so the 0.6.1 npm publish failed with E403. Publish under the kerrshift org scope instead; the installed command stays agentdiff. Update README, npm README, tests and workflow comments.
6 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Renames the npm launcher from
agentdiffto@kerrshift/agentdiff:npx @kerrshift/agentdiff npm i -g @kerrshift/agentdiff # command is still `agentdiff`Why
The v0.6.1 npm publish failed twice:
403 Forbidden - Package name too similar to existing package agent-diff.agent-diffbelongs to an unrelated product, a TypeScript SDK. npm also blocks the same name on PyPI-style similarity rules, so no token can unlock the unscoped name. A name under thekerrshiftorg scope isn't subject to that check, and the user's npm org iskerrshift, matching GitHub.Nothing was ever published to npm under
agentdiff, so no one is broken by the rename.How
npm/package.json:name→@kerrshift/agentdiff, pluspublishConfig.access: public. Scoped packages default to private, and the workflow's--access publicalready covers this; the setting is a second safeguard.publish.ymlcomments all switch to the scoped commands.tests/test_distribution.pyasserts the scoped name, with a comment explaining why.[Unreleased] / Fixedentry explaining that 0.6.1's npm publish never landed.Publishing happens in a separate 0.6.2 release PR, per the release rule.
Testing
Checklist
make lintpassesuv run python -m pytestis greenCHANGELOG.mdentry added under[Unreleased](if feat/fix)type(scope): summary