chore(taiko): revert "chore(taiko): release 2.1.0"

[YoGhurt111]

Reverts #450

[claude]

Claude finished @YoGhurt111's task —— View job

---

PR Review: Revert Release 2.1.0

Review Tasks

• Read and analyze changed files
• Verify revert completeness
• Check for potential issues
• Provide comprehensive review feedback

Review Summary

This PR cleanly reverts the 2.1.0 release (#450) by rolling back two key files:

Changes Analyzed

1. .release-please-manifest.json (1 line changed)

   • ✅ Clean revert: Version rolled back from "2.1.0" → "2.0.0"
   • ✅ Proper format: JSON structure maintained correctly

2. CHANGELOG.md (243 lines removed)

   • ✅ Complete changelog removal: All 2.1.0 release notes removed (lines 3-245)
   • ✅ No orphaned entries: Clean cut at the 2.1.0 section boundary
   • ✅ Preserved history: 1.18.0 and earlier entries remain intact

Code Quality Assessment

✅ Excellent - This is a textbook example of a clean revert:

• Only touches release-specific files (.release-please-manifest.json + CHANGELOG.md)
• No code logic changes that could introduce bugs
• Complete and atomic revert operation
• Maintains git history integrity

Potential Issues

⚠️ Consideration: Release reverts should be coordinated with:

1. Git tags - Check if v2.1.0 tag exists and needs removal
2. Published artifacts - Docker images, binaries, or packages published for 2.1.0
3. Dependencies - Any downstream projects referencing 2.1.0
4. Documentation - Release announcements or changelogs on other platforms

Performance & Security

✅ No concerns - This revert only affects version metadata and documentation.

Test Coverage

N/A - No functional code changes require test updates.

Recommendations

1. ✅ Approve: This revert is technically sound and complete
2. 📋 Process: Ensure proper release coordination (tags, artifacts, communications)
3. 🔄 Follow-up: Consider why 2.1.0 needed to be reverted to prevent similar issues

Final Assessment

LGTM - This is a clean, complete, and safe revert of release metadata. The changes are exactly what you'd expect for reverting a release-please generated release commit.

---