feat(package)!: rename to @deepl/cli and fix stale DeepLcom metadata - #97
Merged
Conversation
Rename the package to the scoped @deepl/cli for the first npm publish (DeepL owns the @DeepL scope; the unscoped names are tombstoned or third-party-held). Add publishConfig.access: "public" — scoped packages default to restricted and the publish fails without it. Point repository/bugs/homepage at github.com/DeepL/deepl-cli instead of relying on the legacy DeepLcom org redirect. The bin name is unchanged: the command is still deepl. The version bump to 2.0.0 is deliberately deferred to the release commit. BREAKING CHANGE: the install string is now `npm install -g @deepl/cli`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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.
Summary
Makes the tarball publishable under its real name: renames the package to the scoped
@deepl/cli, adds thepublishConfigrequired for a public scoped publish, and repoints repository metadata at theDeepLGitHub org instead of the legacyDeepLcomredirect. Second of the three P1s gating the v2.0.0 publish (sync-8mqh.3).Changes Made
package.json"name":deepl-cli→@deepl/cli"publishConfig": { "access": "public" }— scoped packages default to restricted andnpm publishfails without itrepository.url,bugs.url,homepage:github.com/DeepLcom/…→github.com/DeepL/…(three sites, no DeepLcom strings remain)package-lock.json— lockfile-only refresh propagating the renametests/unit/package-manifest.test.ts— newpublish identityblock pinning the scoped name, thedeeplbin name,publishConfig.access: public, and the DeepL-org metadata URLs (written first, TDD)CHANGELOG.md— breaking-change entry under UnreleasedNot in this PR (deliberately): the version bump to 2.0.0 /
VERSIONfile update — that is the final release commit (sync-w79t). Install-instruction retargeting across docs is sync-8mqh.4.Test Coverage
npm pack --dry-runverified: local filename isdeepl-cli-<version>.tgz— npm strips the scope in local filenames, this is expected and not a failed rename. The registry tarball URL followshttps://registry.npmjs.org/@deepl/cli/-/cli-<version>.tgz(scope dropped after/-/), which is the URL form the Homebrew formula needs.Backward Compatibility
❌ Breaking: the install string becomes
npm install -g @deepl/cli(nothing was ever published under the old name, so no installed user is affected).✅ Command unchanged:
binstill mapsdeepl— not a single documented command changes.✅ Tarball contents unchanged: 327 files, same size, README + LICENSE, 0
.mapfiles, 0 internal-name hits.Size: Small ✓
Four-line manifest change plus its pinning tests; the risk is entirely in publish-time behavior, which the acceptance checks cover.
🤖 Generated with Claude Code