fix: wrong metadata branch used in release workflow

[jacekkow]

Rather than getting metadata of the tagged version, it was using data from the latest "nightly" tag.

I have not found any more problematic instances like that.

Summary by CodeRabbit

Bug Fixes

• Fixed the release build process to use the correct release version and tag instead of the nightly branch, ensuring accurate and consistent release builds.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ba764e13-4a90-4435-8eba-cdceb5f423c6

📥 Commits

Reviewing files that changed from the base of the PR and between 592b7de and 1073df8.

📒 Files selected for processing (1)

• .github/workflows/release.yml

💤 Files with no reviewable changes (1)

• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

The release workflow's generate-metadata job no longer explicitly checks out the nightly branch. Instead, it uses the default ref (typically the tag that triggered the release), simplifying the checkout configuration.

Changes

Cohort / File(s)	Summary
Workflow Configuration .github/workflows/release.yml	Removed the ref: nightly override from the actions/checkout@v4 step in the generate-metadata job, allowing it to use the workflow's default ref.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 The nightly branch no longer binds,
Our checkout now more clear-defined,
The tag itself shall be our guide,
Through release workflows, side by side!
Simplicity hops forth with glee, ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: wrong metadata branch used in release workflow' directly and accurately summarizes the main change: correcting the branch/ref used for metadata retrieval in the release workflow.
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

📝 Coding Plan

• Generate coding plan for human review comments

---

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.}

Tip

CodeRabbit can use TruffleHog to scan for secrets in your code with verification capabilities.

Add a TruffleHog config file (e.g. trufflehog-config.yml, trufflehog.yml) to your project to customize detectors and scanning behavior. The tool runs only when a config file is present.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 16.85%. Comparing base (592b7de) to head (1073df8).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #725   +/-   ##
=======================================
  Coverage   16.85%   16.85%           
=======================================
  Files          50       50           
  Lines        3820     3820           
=======================================
  Hits          644      644           
  Misses       3112     3112           
  Partials       64       64           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.