release: v0.20.0

[baezor]

Release v0.20.0

Changes

• docs: clarify video-to-recipe-ai is a CLI tool, not web service (docs: clarify video-to-recipe-ai is a CLI tool, not web service #37)

Summary

This release updates the blog post about the video-to-recipe-ai project to accurately describe it as a CLI tool rather than a web service, with improved CLI usage examples and updated FAQs.

[claude]

Code Review - Release v0.20.0

Summary

This release updates the blog post about video-to-recipe-ai to accurately describe it as a CLI tool rather than a web service. The changes are well-executed and improve the accuracy of the documentation.

---

✅ Positive Observations

1. Accurate Project Description

• The shift from "web service" to "CLI tool" accurately reflects the project's nature
• The "Why a CLI?" section provides clear rationale for the architectural decision
• Transparent about YouTube's IP blocking limitation

2. Improved Documentation Quality

• Added concrete CLI usage examples with actual commands (v2r generate, v2r download, etc.)
• Updated FAQs to reflect CLI functionality (local video file support)
• Enhanced keywords list (added "cli tool", "typescript", "node.js")
• Better metaDescription that accurately describes the tool

3. Content Flow Improvements

• Removed the "From Script to Web Service" and "The YouTube Roadblock" sections that described a failed approach
• Replaced with "How It Works" section showing practical CLI usage
• More focused narrative that doesn't dwell on what didn't work

4. Version Bump

• Properly incremented from v0.19.0 to v0.20.0
• package.json and package-lock.json updated consistently

---

📝 Observations & Suggestions

1. Base Branch Mismatch ⚠️

• Issue: This PR targets main instead of develop
• CLAUDE.md Rule: "Always start from develop branch - Never branch from or commit to main directly"
• GitFlow Violation: Release branches should be created from develop, then merged to both main AND back to develop
• Recommendation: While this is already created, future release PRs should:
  1. Branch from develop
  2. Create PR to main for the release
  3. After merging to main, merge back to develop

2. Missing CI Check Results
According to CLAUDE.md, before merging you should verify:

• ✅ Visual Regression Tests pass (or snapshots intentionally updated)
• ✅ Lighthouse CI scores don't regress
• ✅ All automated checks complete

Please confirm these have passed before merging.

3. Content Accuracy Check

• The blog post mentions "Almost a year ago, I built a CLI tool" but the original version describes building a script, then attempting a web service
• Consider whether the timeline is accurate - was it originally a CLI tool, or was it a script that became a CLI?
• Minor point, but affects narrative consistency

4. Recommended Tools Section

• Removed "Encore.ts" recommendation (appropriate since it's no longer used)
• Consider adding "ffmpeg" to the recommendations since it's mentioned as a requirement
• The README link mentions it's needed, so it could be valuable to highlight

---

🔒 Security Review

✅ No security concerns identified

• Documentation-only changes
• No code execution paths modified
• No credentials or sensitive data exposed

---

🧪 Test Coverage

✅ Appropriate for this change type

• Content changes to a markdown blog post don't require new unit tests
• Visual regression tests should catch any rendering issues
• Lighthouse CI will validate SEO/accessibility

Recommendation: Ensure visual regression tests pass, especially for:

• Blog post rendering (/blog/youtube-to-recipe-with-ai)
• Any text reflow from updated content

---

🎯 Code Quality

✅ Excellent

• Clear, concise writing
• Accurate technical descriptions
• Proper markdown formatting
• SEO-friendly keywords and metadata

---

⚡ Performance Considerations

✅ No performance impact

• Static content changes only
• No new assets added
• No bundle size changes

---

📋 Checklist Before Merge

Based on CLAUDE.md requirements:

• Verify all CI checks pass
• Confirm Visual Regression Tests pass (check for text reflow impacts)
• Confirm Lighthouse CI scores don't regress
• Address base branch concern (this targets main instead of develop)
• After merging to main, ensure changes are merged back to develop

---

🎖️ Overall Verdict

APPROVE with suggestions

The content changes are accurate, well-written, and improve the blog post quality. The version bump is appropriate for a documentation update.

Main concern: GitFlow compliance - this should have targeted develop first per CLAUDE.md guidelines. Since it's already created targeting main, ensure you merge these changes back to develop after releasing.

Recommendation: Merge after confirming CI checks pass, then immediately sync develop with these changes.

---

📚 References

• CLAUDE.md GitFlow workflow
• PR docs: clarify video-to-recipe-ai is a CLI tool, not web service #37 (mentioned in release notes)