Fix build

[fizikiukas]

Summary by CodeRabbit

Release Notes

• Chores
  • Updated internal CI/CD workflow permissions to improve release automation reliability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 767df5c5-9cca-452e-9fee-82e5d27e0508

📥 Commits

Reviewing files that changed from the base of the PR and between f0f8c35 and bf9a6d5.

📒 Files selected for processing (2)

• .github/workflows/build-release.yaml
• .github/workflows/release.yaml

---

📝 Walkthrough

Walkthrough

This PR adds explicit workflow-level permissions to two GitHub Actions release workflows. Both .github/workflows/build-release.yaml and .github/workflows/release.yaml now declare permissions: contents: write to grant their token sufficient rights for tag creation and release operations.

Changes

Workflow Permissions

Layer / File(s)	Summary
Workflow permissions blocks .github/workflows/build-release.yaml, .github/workflows/release.yaml	Both workflows add a top-level permissions block granting contents: write to ensure sufficient token rights for tag bumping and GitHub release creation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Fix build' is vague and lacks specificity about what aspect of the build is being fixed. While it relates to the changeset (permissions for workflows), it doesn't convey the actual nature of the fix.	Use a more descriptive title such as 'Add explicit permissions to GitHub Actions workflows' or 'Fix workflow permissions for release jobs' to clearly communicate the specific change being made.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/build

---

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