release-revoke

To rollback a published npm release and delete the git tag, you need to revoke the GitHub release, delete both local and remote git tags, and deprecate the npm package version to discourage installation.

Deprecating an npm package version during a release rollback discourages new installations of that specific version while leaving the published artifact intact, ensuring consumers are warned about the misreleased package.

Yes, you can optionally revert a release commit if it is the latest commit on the release branch, ensuring the repository state is cleaned up alongside the GitHub release and git tag deletion.

The best way to safely revoke a misreleased npm version is to verify the state across GitHub, git tags, and npm, prompt for confirmation, and execute the rollback steps in order with safe fallbacks.

No, you do not need to manually clean up git tags when rolling back a release, because the rollback process automatically deletes both local and origin git tags associated with the target version.