Synchronize versioning and enhance release creation process

[Lashen1227]

Depends #34

Summary by CodeRabbit

• New Features

  • Release builds now sync the app version automatically from the release tag before packaging.
  • GitHub Releases are now created directly during the release process with auto-generated notes.

• Changes

  • The release flow no longer uses the previous changelog generation step.

[coderabbitai]

📝 Walkthrough

Walkthrough

The release workflow now derives a VERSION from RELEASE_VERSION and applies it via npm version without git tagging, then creates a GitHub Release using gh release create with auto-generated notes. The prior changelog generation step using npx changelogithub is removed.

Changes

Release Workflow Update

Layer / File(s)	Summary
Version sync and release creation .github/workflows/release.yml	Adds a "Sync version" step deriving VERSION from RELEASE_VERSION and applying it via npm version (no git tag), and a "Create GitHub Release" step using gh release create with auto-generated notes; removes the prior changelog generation step using npx changelogithub.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: version synchronization and an improved release creation flow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/actions-workflow

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/release.yml:
- Around line 51-56: The “Create GitHub Release” step is running too early in
the release workflow, before npm tag determination and npm publish succeed. Move
the release creation logic in the workflow so it happens after the publish path
completes successfully, or gate it on the publish step result. Use the existing
“Create GitHub Release”, “Determine npm tag”, and “Publish to npm” steps in
release.yml to reorder the flow and avoid creating a release when publish later
fails.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 34b728c3-d491-44a1-8992-9c6a6c12f5ac

📥 Commits

Reviewing files that changed from the base of the PR and between df7b506 and caedaac.

📒 Files selected for processing (1)

• .github/workflows/release.yml