Repository navigation
fix(deps): move to @todoist/twist-sdk - #245
Merged
Merged
Conversation
@doist/twist-sdk is no longer released; @todoist/twist-sdk@4.0.0 is the same code as @doist/twist-sdk@3.0.1 under the new name. Swap the dependency (2.9.4 -> 4.0.0) and every import, the jest transformIgnorePatterns entry and the README reference. This crosses twist-sdk 3.0.0, whose only breaking change is requiring Node >=24 and npm >=11. This package already declares the same engines, so no code changes were needed and tool behaviour and output are unchanged.
doist-release-bot Bot
added a commit
that referenced
this pull request
Nov 11, 2026
## [8.0.1](v8.0.0...v8.0.1) (2026-11-11) ### Bug Fixes * **deps:** move to @todoist/twist-sdk ([#245](#245)) ([b3b3ef0](b3b3ef0))
Contributor
|
🎉 This PR is included in version 8.0.1 🎉 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.
Why
@doist/twist-sdkis no longer released. The SDK now publishes as@todoist/twist-sdk, and@todoist/twist-sdk@4.0.0is the same code as@doist/twist-sdk@3.0.1under the new name.What changed
@doist/twist-sdk@2.9.4→@todoist/twist-sdk@4.0.0(pinned exactly, as before). The lockfile diff only swaps the SDK entry (and its nestedzod@4.1.12, which is unchanged).@doist/twist-sdkimport across the tools, helpers, tests andscripts/run-tool.tsnow points at@todoist/twist-sdk. oxfmt re-sorted the imports in a few files because of the scope change.transformIgnorePatternsnow allows@todoist/twist-sdkthrough the transform instead of@doist/twist-sdk.Breaking changes crossed
Moving from 2.9.4 to 4.0.0 crosses twist-sdk 3.0.0, whose only breaking change is requiring Node >=24 and npm >=11 (todoist/twist-sdk-typescript#163). This package already declares
node >=24/npm >=11and CI already runs on Node 24 and 26, so no code migration was needed. The source diff between 2.9.4 and 3.0.1 has no API changes (only a comment URL), so tool behaviour and tool output are unchanged.Checked locally
npm run type-check: passesnpm test: 21 suites, 216 tests and 53 snapshots pass, with no snapshot changesoxlintandoxfmt --check: cleanRelated
Renovate's #218 ("update production dependencies (major)") bumps
@doist/twist-sdk2.9.4 → 3.0.0 alongsidedotenv. Once this lands, its@doist/twist-sdkbump is superseded; I haven't touched it.No other
@doist/*packages remain in this repo's dependencies.