fix: use release branch and PR for version bump to respect branch pro…

[Git-HimanshuRathi]

Summary

The manual desktop release workflow was failing because it attempted to push directly to main, which is protected.
This PR updates the workflow to use a release branch + PR-based flow, fully respecting branch protection rules.

Fixes #903

---

What changed

• Create a versioned release branch (release/vX.Y.Z) instead of pushing to the target branch
• Automatically open a PR from the release branch to the triggering branch
• Skip PR creation if one already exists (safe re-runs)
• Run build and release jobs against the release branch
• Add pull-requests: write permission
• Document tag creation behavior in the auto-generated PR

---

Why this approach

• Works with protected branches
• Keeps release changes auditable via PRs
• Matches GitHub’s recommended workflow
• Avoids force pushes or bypassing rules

---

Code Understanding and AI Usage

• Yes, I used AI assistance
• I reviewed and understand every line of the code
• I tested the workflow and considered edge cases

---

Checklist

• Linked the issue
• Self-reviewed the code
• Changes follow project conventions
• I can explain all added logic

Summary by CodeRabbit

• Chores
  • Improved release workflow with enhanced version management and automated pull request handling for releases.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for circuitverse ready!

Name	Link
🔨 Latest commit	d9ac7bf
🔍 Latest deploy log	https://app.netlify.com/projects/circuitverse/deploys/697f51f83322bb000876afa7
😎 Deploy Preview	https://deploy-preview-904--circuitverse.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 47 (🔴 down 1 from production) Accessibility: 73 (no change from production) Best Practices: 92 (no change from production) SEO: 82 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

The pull request modifies the Tauri release workflow in .github/workflows/Tauri-Release.yml to implement a release branch strategy. It adds pull-request write permissions, introduces a release_branch output from the version job, and restructures the workflow to create a release branch (release/$NEW_VERSION) and open a pull request targeting the original branch instead of committing directly to the main branch. Subsequent workflow steps are updated to reference this generated release branch through needs.version.outputs.release_branch rather than using github.ref_name, ensuring the entire pipeline operates on the release branch.

Possibly related PRs

• Release Pipelines with Code Signing #636: Modifies the same Tauri-Release workflow file and version job with different branch handling approach for release operations.

🚥 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 references the main change (release branch and PR for version bump) and directly relates to the changeset's primary objective of respecting branch protection rules.
Linked Issues check	✅ Passed	All coding requirements from issue #903 are met: release branch creation, PR opening from release branch, and workflow updates to use the release branch instead of direct pushes.
Out of Scope Changes check	✅ Passed	All changes directly address the linked issue requirements; no unrelated modifications to functionality or structure were introduced.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[ThatDeparted2061]

attach some screenshots please

[Git-HimanshuRathi]

test results :

Link : https://github.com/Git-HimanshuRathi/cv-frontend-vue/actions/runs/21563030854

it created pull request :

Link : Git-HimanshuRathi#1
release page :

Link : https://github.com/Git-HimanshuRathi/cv-frontend-vue/releases/tag/v0.0.4

[Git-HimanshuRathi]

version got bumped , reverted it back to 0.0.0 .

[Git-HimanshuRathi]

@ThatDeparted2061 @tachyons ready for review .

[ThatDeparted2061]

Nice good work

[ThatDeparted2061]

@tachyons LGTM

[Git-HimanshuRathi]

@tachyons PR has been approved by harsh .