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

[mateoradman]

Potential fix for https://github.com/mateoradman/bazarr-bulk/security/code-scanning/4

To fix the issue, add a permissions block with minimal permissions required for this workflow. For most Rust CI jobs, contents: read is adequate—this allows necessary read access to repository contents, which is needed for code checkout and read-only operations, but does not grant write permissions. This block can be added at the top level (affecting all jobs unless overridden), or to individual jobs (such as the test job). The recommended way is to add it at the root of the workflow, directly after the name and before any on, env, or jobs blocks.

No imports or method changes are needed. The workflow file should be updated by inserting the following lines:

permissions:
  contents: read

directly after the name: Rust CI line.

---

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

[Copilot]

Pull Request Overview

This PR enhances the security configuration of the Rust CI workflow by adding explicit permissions settings. The change follows GitHub Actions best practices by limiting the workflow to read-only access to repository contents.

• Adds explicit permissions block with contents: read to restrict workflow permissions

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.