Repository navigation
feat!: publish as @todoist/comms-cli - #119
Merged
Merged
Conversation
The package moves from the @Doist npm scope to @todoist. The binary stays tdc. - Rename the package to @todoist/comms-cli and point the release workflow's setup-node scope at @todoist. - Switch @doist/cli-core 1.10.0 to @todoist/cli-core 2.0.0 (same code, the major is only the rename) across imports, mocks, the vitest inline list and the docs. - Update install, uninstall and @next commands in the README, CONTRIBUTING and docs, and note in the README that the old package must be uninstalled first because both install tdc. @doist/comms-sdk stays at 3.11.0, and the OAuth client metadata URLs are unchanged. BREAKING CHANGE: the package is now published as @todoist/comms-cli; replace @doist/comms-cli with @todoist/comms-cli in dependencies and imports.
doistbot
reviewed
Nov 11, 2026
doistbot
left a comment
Member
There was a problem hiding this comment.
This PR updates feat!: publish as @todoist/comms-cli. No issues were flagged in the reviewed diff.
Contributor
|
🎉 This PR is included in version 5.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Short description
The package moves from
@doist/comms-clito@todoist/comms-cli. The existing release workflow publishes it via OIDC trusted publishing, so merging this releases 5.0.0 under the new name. It's a major version because anyone depending on the package has to switch their dependency and imports to@todoist/comms-cli, and anyone with the CLI installed globally has to uninstall@doist/comms-clibefore installing the new one, since both installtdc. The old@doist/comms-clipackage stays on npm for now and will be deprecated pointing at the new one.Before merging:
@todoist/comms-clihas to exist on npm with a trusted publisher pointing at this repo'srelease.yml. When this PR was opened, the registry returned 404 for@todoist/comms-cli, so the release would fail to publish if this merged first.This is a plain rename. It supersedes the npm scope part of #116 and leaves its release redesign and comms-sdk 4 upgrade out.
package.jsonandpackage-lock.jsonnow name@todoist/comms-cli. The version stays 4.1.3, and thefeat!:commit makes semantic-release cut 5.0.0.@doist/cli-core1.10.0 is replaced by@todoist/cli-core2.0.0, pinned exactly as before. It's the same code as@doist/cli-core1.10.x, and the major is only the rename. Every import, subpath import (/auth,/commands,/testing, …),vi.mockand type import moves to the new name, as does theserver.deps.inlineentry invitest.config.ts. The lockfile was regenerated withnpm install --package-lock-only --ignore-scripts. Apart from the rename, the only change is that cli-core's optional@napi-rs/keyringdependency is now hoisted to the top-levelnode_modules, at the same versions and integrity hashes. Swapping the scope changed the import order in one file, so the changed files were formatted with the pinnedoxfmt0.72.0.setup-nodescopeis now@todoist. Nothing else inrelease.ymlchanges.@nextinstall in CONTRIBUTING,docs/SPEC.md, and the cli-core mentions inAGENTS.md,CODEBASE.mdand the agent checks and skills. The README now says the package was previously published as@doist/comms-cliand that the old package needs to be uninstalled first, because both installtdc.tdc updateand the doctor update check read the package name frompackage.jsonat runtime, so they now check@todoist/comms-cliwithout any code changes.These are left as they are:
@doist/comms-sdk3.11.0 and its imports.@todoist/comms-sdkis now 5.0.0 (the 4.x API line), a major version ahead of what this CLI uses, so it moves separately. The same goes for theupdate-comms-sdkworkflow.oauth/client-metadata.jsonandOAUTH_CLIENT_ID/LOGO_URIinsrc/lib/auth-constants.ts, along with their tests. Todoist binds tokens to theseraw.githubusercontent.com/Doist/comms-cli/...URLs, which aren't package names.tdcbinary, thecomms-cliskill name, the config path, and theDOIST_*secrets.CHANGELOG.mdhistory andLICENSE.