Skip to content

feat!: publish as @todoist/twist-ai - #243

Merged
scottlovegrove merged 1 commit into
mainfrom
scottl/todoist-npm-scope
Nov 11, 2026
Merged

scottlovegrove merged 1 commit into
mainfrom
scottl/todoist-npm-scope

Conversation

@scottlovegrove

@scottlovegrove scottlovegrove commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

Short description

The npm package moves from @doist/twist-ai to @todoist/twist-ai. The @todoist/twist-ai package already exists on npm with a trusted publisher pointing at this repo's release workflow, so once this merges the release publishes a new major version (8.0.0) under the new name. The old @doist/twist-ai package stays on npm for now and will be deprecated later, pointing at the new one. Consumers need to switch their dependency and imports to @todoist/twist-ai, and MCP client configs need npx -y @todoist/twist-ai. It's a major release because consumers have to switch their dependency and imports to the new name.

  • package.json / package-lock.json: name is now @todoist/twist-ai (the root name entries in the lockfile too). The version is unchanged so semantic-release carries on from the existing tags.
  • Release workflow: actions/setup-node now uses scope: '@todoist' so publishing the new name works. @doist/twist-sdk installs from the public npm registry without a scope mapping.
  • README: the install command, the import example, the npx quick start, and the Claude Desktop, Cursor, Claude Code and VS Code MCP configs. There's one line under the install section saying the package was previously published as @doist/twist-ai.
  • Release notes fix: conventional-changelog-conventionalcommits is pinned back from 10.4.0 to 9.3.1, the version the other repos use, and the lockfile is regenerated (the only changes are that package, its @conventional-changelog/template dependency being swapped for the already-present compare-func, and the root name). The last release (run) failed in semantic-release's generateNotes step with Missing helper: "conventional-changelog-conventionalcommits requires conventional-changelog-writer@9 or newer, because @semantic-release/release-notes-generator (even the latest 14.1.1) still uses writer 8. Without this the release under the new name would fail the same way.

These are left as they are:

  • the @doist/twist-sdk (2.9.4) dependency and its imports: this repo is a major version behind on it, so it'll move to @todoist/twist-sdk when it's bumped
  • the twist-ai binary, mcpName (net.twist/mcp) and the MCP server name
  • the DOIST_RELEASE_BOT_* secrets, the author field and LICENSE
  • CHANGELOG.md history

The npm package moves from the @Doist scope to @todoist. Rename the
package, point the release workflow's registry scope at @todoist, and
update the install command, import example and MCP client configs in
the README.

Also pin conventional-changelog-conventionalcommits back to 9.3.1.
Version 10 needs conventional-changelog-writer 9, but
@semantic-release/release-notes-generator still uses writer 8, so the
last release failed in generateNotes with "Missing helper".

The @doist/twist-sdk dependency stays on the old scope for now, as
this repo is a major version behind on it.
@scottlovegrove scottlovegrove self-assigned this Nov 11, 2026
@scottlovegrove scottlovegrove changed the title fix: publish as @todoist/twist-ai feat!: publish as @todoist/twist-ai Nov 11, 2026
@scottlovegrove
scottlovegrove merged commit 1952e3b into main Nov 11, 2026
5 checks passed
@scottlovegrove
scottlovegrove deleted the scottl/todoist-npm-scope branch November 11, 2026 12:21
doist-release-bot Bot added a commit that referenced this pull request Nov 11, 2026
## [7.0.1](v7.0.0...v7.0.1) (2026-11-11)

### Bug Fixes

* **ci:** use the todoist GitHub org after the rename ([#242](#242)) ([d47644a](d47644a))
* publish as @todoist/twist-ai ([#243](#243)) ([1952e3b](1952e3b))
@doist-release-bot

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 7.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant