Write github permission to add tags and releases

[agneym]

Summary by CodeRabbit

• Chores
  • Enhanced release automation workflow configuration.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 85d6840

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The GitHub Actions release workflow permissions configuration is updated to grant write access to the contents permission, enabling the workflow token to perform content-modification operations during release automation.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration .github/workflows/release.yml	Updated permissions.contents from read to write to enable write access for release automation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify that write access to contents is necessary and intended for the release workflow
• Confirm no unintended security implications from the elevated permission scope

Poem

🐰 A token's wings now spread so wide,
With write access as its trusted guide—
The workflow dances, swift and true,
Releasing magic, fresh and new! ✨

Pre-merge checks and finishing touches

✅ 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 clearly describes the main change: updating GitHub workflow permissions to allow writing tags and releases.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/write-permissions-github

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9a81198 and 85d6840.

📒 Files selected for processing (1)

• .github/workflows/release.yml (1 hunks)

🔇 Additional comments (1)

.github/workflows/release.yml (1)

10-10: LGTM! This change is necessary for release automation.

The contents: write permission is required for the changesets/action to function, as it needs Contents - Read and Write access. The action has a createGithubReleases parameter (default true) to create Github releases after publish, which aligns with the PR objective to enable tag and release creation.

---

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