Release v10.5.1

[asjohnston-asf]

TODO

• update MONTHLY_BUDGET secret value for hyp3-edc-prod environment

To fix the issue, we will add a permissions block at the root level of the workflow. This block will specify the minimal permissions required for the workflow to function. Since the workflow is related to checking changelogs, it likely only needs contents: read permission to access repository contents. This change ensures that the GITHUB_TOKEN has restricted access, reducing the risk of unintended actions.

---

To fix the issue, we will add a permissions block at the root of the workflow file. This block will specify the minimal permissions required for the workflow to function. Based on the context, the workflow likely only needs contents: read permissions, as it is checking labels on pull requests and does not appear to modify repository contents or perform other write operations.

---

[github-actions]

Developer checklist

• Indicated the level of changes to this package by affixing one of these labels:
  • major -- Major changes to the API that may break current workflows
  • minor -- Minor changes to the API that do not break current workflows
  • patch -- Patches and bugfixes for the current version that do not break current workflows
  • bumpless -- Changes to documentation, CI/CD pipelines, etc. that don't affect the software's version
• (If applicable) Updated the dependencies and indicated any downstream changes that are required
• Added/updated documentation for these changes
• Added/updated tests for these changes
• Verified changes in test deployment and summarized results, e.g. in PR description or comments on the related issue(s)
• If the step function code has changed, have you drained the job queue before merging?
  • For example, if the interface for a Lambda function has changed to expect different input,
    then currently running jobs (which use the old step function definition) will call the new
    function with the old input. So we must drain the job queue before deployment, so that the new
    function is only called by the new step function definition.

Reviewer checklist

• Have all dependencies been updated?
• Is the level of changes labeled appropriately?
• Are all the changes described appropriately in CHANGELOG.md?
• Has the documentation been adequately updated?
• Are the tests adequate?
• Have the changes been verified in the test deployment?