Repository navigation
fix(ci): use the todoist GitHub org after the rename - #178
Merged
Merged
Conversation
The Doist GitHub organisation is now todoist. npm provenance checks package.json's repository URL against the repository that publishes, so a URL still naming Doist/cli-core makes the next release fail. Point package.json, the Renovate preset, the issue project URL, and the GitHub links in the README, docs and code examples at todoist.
doist-release-bot Bot
added a commit
that referenced
this pull request
Nov 11, 2026
## [1.10.1](v1.10.0...v1.10.1) (2026-11-11) ### Bug Fixes * **ci:** use the todoist GitHub org after the rename ([#178](#178)) ([d1126cf](d1126cf))
Contributor
|
🎉 This PR is included in version 1.10.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.
The Doist GitHub organisation was renamed to todoist at 10:00 UTC on 2026-11-11. GitHub Actions doesn't follow the old owner, and npm provenance checks
package.json'srepositoryURL against the repository that publishes, so withrepositorystill namingDoist/cli-corethe nextnpm publishfromtodoist/cli-corewould fail with E422. The npm trusted publisher for@doist/cli-corealready points attodoist/cli-core.This swaps the GitHub owner references from
Doisttotodoist:package.json:repository,homepageandbugs. semantic-release and npm provenance read the repository URL from here.github>todoist/renovate-config:frontend-basepreset.https://github.com/orgs/todoist/projects/83.actions/add-to-projectlooks the project up by organisation login, which doesn't follow the rename. The release workflow had noDoist/...actions, owners or checkouts.repoUrlexamples in the README andchangelog.ts, the README'sofficialSourceexample (owner: 'todoist'), the owner-qualified selector in asource.tscomment, and the reviewer brief's repository name.clientUrisample. cli-core doesn't build anyDoistGitHub URL itself:repoUrl,brewFormulaandofficialSourceall come from the CLI that calls it.docs/agents.md.These are left as they are:
@doistnpm scope, which has its own migrationCHANGELOG.mdhistory andLICENSEDoist/td-goalsrepositories andofficialSource: { owner: 'Doist' }fixtures: sample data for the parser and the official-source check, tied together, with no real repository behind thembrewFormulaexamples and test (doist/tap/todoist-cli), which is the name a user tapped locally rather than a URLdoist-platform/doist-version/doist-osrequest headers, thedoist-cli-extensionsuser agent and theDOIST_RELEASE_BOT_*secretsFollow-up outside this repo: todoist-cli passes
officialSource: { host: 'github.com', owner: 'Doist' }, and cli-core matches the owner exactly, so an extension installed fromtodoist/...won't get the Todoist marker until that changes.