v2.0.0

🚀 LyricFlow v2.0.0 — Major Release

This is the first major release of LyricFlow since the initial v1.0.0 launch. While the core idea remains the same, a lot has changed under the hood to make releases safer, more reliable, and easier to manage going forward.

🔧 What’s Changed Since v1.0.0
Release & Versioning System (Major overhaul)

Introduced proper Semantic Versioning (Patch / Minor / Major).

Built a fully automated one-click release pipeline using Automator:

Choose Patch / Minor / Major at release time.

Automatically bumps versions across:

package.json

Cargo.toml

tauri.conf.json (Tauri v2–compatible)

Prevents accidental double-bumps or version mismatches.

Release Notes Workflow

Added an interactive prompt during release to write custom release notes.

Notes are attached directly to the GitHub release.

Supports multi-line notes (What’s new / Fixes / Notes).

Safe to edit release notes later without affecting future releases.

GitHub Releases & CI

Git tags are now the single source of truth for releases.

GitHub Actions reliably trigger on version tags.

Builds are generated and attached automatically to each release.

Fixed edge cases where releases existed but builds didn’t fire.

Tauri v2 Configuration Fixes

Migrated away from deprecated Tauri v1 config fields.

Ensured tauri.conf.json uses top-level version as required by Tauri v2.

Eliminated config validation errors during CI builds.

Stability & Safety Improvements

Added safeguards to stop releases if version files are already modified.

Prevented corrupted config files during automated version updates.

Improved logging so failures are visible and debuggable.

🧭 Why v2.0.0?

This release doesn’t radically change what LyricFlow does — it changes how confidently it can be developed and released.

From this point on:

Releases are predictable.

Version history is trustworthy.

CI builds are reliable.

Release notes are intentional, not an afterthought.

That’s a breaking change in workflow — and worth a major version.