Release v0.6.1

[jacquelynsmale]

No description provided.

To fix this issue, an explicit permissions block should be added to the job definition that calls the reusable workflow. This block should grant only the minimum permissions required by the job/reusable workflow. Since we do not know precisely what permissions the reusable workflow needs, a safe minimal starting point based on best practice is contents: read (to allow reading repo content) and, if necessary, more restrictive/targeted permissions. The block should be added under the job definition (call-changelog-check-workflow) at line 15 or 16, preceding the uses: line. No other code changes, imports, or definitions are required.

To fix the problem, add a permissions block to the job or at the root of the workflow, specifying the minimal privileges required. Since this workflow calls a reusable PR-label-check workflow (likely performing read-only checks on PR labels or metadata), the minimal starting point is contents: read. If the called workflow requires more (for example, modifying labels), we may also need pull-requests: write. Within the context given, the block should be added under the job's definition (call-labeled-pr-check-workflow) as a sibling to uses: (recommended for jobs that use reusable workflows). No imports or additional code is needed; only YAML key/value pairs added at the correct place.

---

[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)

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?