ci: Add 'issues: write' permission to the changesets_release workflow

[alco]

The release workflow was failing to comment on Issues linked in the changelogs (while PR comments worked fine). This was due to the GITHUB_TOKEN lacking the explicit issues: write permission required for the gh issue comment command.

Problematic Output:

Found 3 linked issues to comment on
GraphQL: Resource not accessible by integration (addComment)
  Failed to comment on issue #3669: Command failed: gh issue comment 3669 --repo electric-sql/electric --body-file -
GraphQL: Resource not accessible by integration (addComment)
  Failed to comment on issue #3639: Command failed: gh issue comment 3639 --repo electric-sql/electric --body-file -
GraphQL: Resource not accessible by integration (addComment)
  Failed to comment on issue #3677: Command failed: gh issue comment 3677 --repo electric-sql/electric --body-file -

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow permissions to enable release automation to comment on GitHub issues.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Added a issues: write permission to the GitHub Actions changesets release workflow, allowing the changesets tool to comment on issues during release processes.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration .github/workflows/changesets_release.yml	Added issues: write permission to enable changesets to post comments on issues during release

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A whisker-twitch of workflows fine,
One permission line, so divine,
Now changesets can chat with glee,
On issues for all to see!
✨🎉

🚥 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 accurately describes the main change: adding 'issues: write' permission to the changesets_release workflow to fix a permission error preventing issue comments during releases.
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.}

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bbaf243 and 3a9072a.

📒 Files selected for processing (1)

• .github/workflows/changesets_release.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: Test packages/experimental w/ sync-service
• GitHub Check: Test packages/react-hooks w/ sync-service
• GitHub Check: Test packages/y-electric w/ sync-service
• GitHub Check: Test packages/typescript-client w/ sync-service
• GitHub Check: Test packages/start w/ sync-service
• GitHub Check: Run Lux integration tests

🔇 Additional comments (1)

.github/workflows/changesets_release.yml (1)

10-14: LGTM!

The addition of issues: write permission is the correct fix for the GraphQL permission error when commenting on issues. The permission is appropriately scoped and follows the principle of least privilege. The inline comment clearly documents the purpose, consistent with the other permission declarations.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.21%. Comparing base (cb9f571) to head (3a9072a).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #3707       +/-   ##
===========================================
+ Coverage   76.32%   87.21%   +10.89%     
===========================================
  Files          11       23       +12     
  Lines         604     1987     +1383     
  Branches      148      527      +379     
===========================================
+ Hits          461     1733     +1272     
- Misses        142      252      +110     
- Partials        1        2        +1     

Flag	Coverage Δ
packages/experimental	87.73% <ø> (ø)
packages/react-hooks	86.48% <ø> (ø)
packages/start	82.83% <ø> (-6.76%)	⬇️
packages/typescript-client	93.35% <ø> (?)
packages/y-electric	56.05% <ø> (ø)
typescript	87.21% <ø> (+10.89%)	⬆️
unit-tests	87.21% <ø> (+10.89%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.