Potential fix for code scanning alert no. 19: Workflow does not contain permissions

[Dargon789]

Potential fix for https://github.com/Dargon789/foundry/security/code-scanning/19

To fix the issue, we need to explicitly define the permissions for the GITHUB_TOKEN in the issue job. Since the job uses the JasonEtco/create-an-issue@v2 action, it requires issues: write permissions. Additionally, we should set other permissions to read or remove them entirely if they are not needed. This ensures that the job adheres to the principle of least privilege.

The permissions block should be added to the issue job, specifying issues: write and contents: read (the latter is often required for basic repository access).

---

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

Summary by Sourcery

Bug Fixes:

• Add permissions block to the issue job with issues: write and contents: read to address the code scanning alert for missing workflow permissions.

[sourcery-ai]

Reviewer's Guide

The PR updates the release workflow to adhere to the principle of least privilege by explicitly defining GITHUB_TOKEN permissions for the issue job, adding a permissions block with issues: write and contents: read.

File-Level Changes

Change	Details	Files
Explicitly define GitHub token permissions for the issue job	Added a permissions block under the issue job Set issues: write permission Set contents: read permission	.github/workflows/release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Dargon789 - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}