Repository navigation
fix(ci): use the todoist GitHub org after the rename - #118
Merged
Merged
Conversation
The Doist GitHub organisation is now todoist. Actions doesn't follow the old owner, so the release job fails to resolve the Comms announcement action, and npm provenance rejects a repository URL that doesn't match the publishing repo. Point the release and issue-automation workflows, the Renovate preset, package.json's repository, homepage and bugs, the changelog footer link, the sign-in page's GitHub link and the links in docs at todoist. Prose that meant the company now says Todoist. The OAuth client ID metadata document and its URLs stay on the old owner: tokens are bound to the client_id URL, which still resolves.
doist-release-bot Bot
added a commit
that referenced
this pull request
Nov 11, 2026
## [4.1.2](v4.1.1...v4.1.2) (2026-11-11) ### Bug Fixes * **ci:** use the todoist GitHub org after the rename ([#118](#118)) ([700e176](700e176))
Contributor
|
🎉 This PR is included in version 4.1.2 🎉 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, so the release job fails while it's being set up, before any step runs, because
Doist/comms-actionsno longer resolves. npm provenance also checkspackage.json'srepositoryURL against the repository doing the publish, which is nowtodoist/comms-cli, sonpm publishwould fail with E422 even with the action fixed. The npm trusted publisher for@doist/comms-clialready points attodoist/comms-cli.This swaps the GitHub owner references from
Doisttotodoist:aeeefe32…exists intodoist/comms-actions), and the project URL in the issue automation workflow, whichactions/add-to-projectresolves through the organisation login.github>todoist/renovate-configpreset.package.json:repository,homepageandbugs.tdc changelogfooter link and the "View on GitHub" link on the sign-in result page. The changelog test expectation matches.CODEBASE.md,docs/icon.mdand the reviewer brief.These are left as they are:
oauth/client-metadata.json) andOAUTH_CLIENT_ID/LOGO_URIinauth-constants.ts. Todoist binds every token it issues to the exactclient_idURL, so moving it toraw.githubusercontent.com/todoist/...would break refresh for every existing login, and changing the document onmainwould break sign-in for every released version still sending the old URL. The oldraw.githubusercontent.com/Doist/comms-cli/...URLs still serve the files directly, so nothing is broken today. Itsclient_uriandlogo_uristay with it.CHANGELOG.mdhistory andLICENSE@doistnpm scope, theauthorfield and the skill'sauthor: Doist, the release bot identity, theDOIST_*andCOMMS_DOISTBOT_*secret names, thedoist-*usage headers, references to the Doist Secrets Management Standard, and sample content such as theDoistworkspace and@doist.comemails in examples and testsThis only renames the GitHub owner so releases work in the meantime; the npm scope migration stays in #116.