fix: Remove dual publishing to GitHub Packages

[gnapse]

Summary

• Removes dual publishing to GitHub Packages from the publish workflow
• Removes .npmrc file since it's no longer needed

Problem

The v5.6.0 release failed because the workflow attempts to publish to both npmjs.org and GitHub Packages. The GitHub Packages publish step failed with an authentication error, preventing the release from completing.

Looking at the logs, the package was never actually published to npm - the failure happened before npm publish completed.

Background

Dual publishing was added in #158 (Oct 2022, 2.5 years ago) to support internal projects that pulled @doist packages from GitHub Packages. Since this is a public package, there's no reason internal projects can't simply pull it from npmjs.org like everyone else.

Changes

• Remove GitHub Packages publishing step from workflow
• Remove .npmrc file (was only needed for GitHub Packages registry config)

Next Steps

After merging, we'll need to delete and recreate the v5.6.0 release to re-trigger the workflow.

🤖 Generated with Claude Code

[scottlovegrove]

👍🏻

Worth noting that if you have a project that "requires" it to be on github, this is likely due to your package-lock.json file. Make a note of what version of the SDK you're using, then do npm remove @doist/todoist-api-typescript && npm i @doist/todoist-api-typescript@<your_version> and this should pull it from npmjs and you're good to go.