v8.0.2

🪲 [Fix]: Obsolete GitHub token write permissions removed (#521)

Repositories that use the GitHub App permission model can run Process-PSModule without granting unneeded repository, pull-request, or status write access. GitHub Pages deployments continue to use the caller's github.token with contents: read, pages: write, and id-token: write.

Fixed: Reusable workflow permission escalation

The reusable workflow no longer requests permissions that GitHub App installation tokens already provide for release and pull-request operations. Update caller workflows to use the narrowed permission block documented for v8.

permissions:
  contents: read
  pages: write
  id-token: write

---

Technical details

• Removed legacy github.token write requests from the reusable workflow and nested jobs; scoped GitHub App tokens retain repository and pull-request write access.
• Updated repository workflow tests and caller documentation to use the v8 permission contract.

Changed surface	Standards checked	Framework docs checked	Result
.github/workflows/**	GitHub Actions	Reusable workflow contract	Fixed in this PR
docs/content/**	Markdown, Natural Language	Workflow setup guides	Fixed in this PR

Relevant issues (or links)

Related work

• References #510