// Rollback a failed release by deleting tags and reverting version changes. Use when a release fails, needs to be cancelled, or when reverting a problematic release.
| name | release-rollback |
| description | Rollback a failed release by deleting tags and reverting version changes. Use when a release fails, needs to be cancelled, or when reverting a problematic release. |
Rollback a failed release by deleting the release and reverting version changes.
ā ļø This will delete the release and revert version changes.
Check recent tags:
git tag -l --sort=-version:refname | head -5
Review which version needs to be rolled back.
Confirm with the user:
Execute the rollback command:
npm run release:rollback <version>
Example:
npm run release:rollback 1.5.0-beta.3
The rollback script performs:
Post-rollback verification:
git tag -lnpm run release:check to validate fixesOnce issues are fixed, create new release:
npm run build to testnpm run test:smokenpm run lint to auto-fixnpm run type-check to verifynpm run release:check# Rollback beta release
/release-rollback 2.0.0-beta.3
# Rollback stable release
/release-rollback 1.5.0
This requires the version number to rollback.
Before proceeding with rollback:
After rollback:
Create a beta pre-release for community testing with intelligent version detection. Use when creating beta releases, publishing pre-releases, or preparing versions for community testing.
Create a stable production release with intelligent detection (finalize beta or direct release). Use when publishing stable releases, finalizing beta versions, or creating production releases.
Debug errors, bugs, and unexpected behavior systematically in Home Assistant integration. Use when investigating errors, analyzing stack traces, fixing bugs, or troubleshooting unexpected behavior.
Implement approved plans with precision and quality for Linus Dashboard Home Assistant integration. Use when implementing features, executing approved plans, writing code following standards, or developing new functionality.
Check if project is ready for release with comprehensive pre-release validation. Use when verifying release readiness, running validation checks, or checking project quality before publishing.
Review code quality, security, and maintainability before committing. Use when reviewing code changes, checking code quality, performing security review, or validating changes before commit.