mirror of
https://github.com/expo/eas-cli.git
synced 2026-11-15 17:31:46 -10:00
## Summary Updates the codemention GitHub Action pin from `v1.4.0` to a reviewed post-`v1.5.2` upstream commit: - `tobyhs/codemention@ebac5877393ab8693fd73b42708c8552043e9a3b` - keeps the action pinned to an immutable commit SHA because this workflow runs on `pull_request_target` with `pull-requests: write` - avoids pinning to moving `main` or a mutable tag ## Security review I reviewed upstream `tobyhs/codemention` changes from `v1.4.0` through `v1.5.2` and found that `v1.5.2` introduced `[email protected]`, which currently has critical/high production dependency advisories. I therefore did not pin to `v1.5.2`. The selected post-release commit includes follow-up dependency fixes on upstream `main`, including `[email protected]`, `[email protected]`, and `[email protected].0`. `npm audit --omit=dev` on that upstream commit reported 0 vulnerabilities at review time. ## Validation - `yarn fmt:check .github/workflows/codemention.yml` - YAML parse check - `git diff --check`
21 lines
832 B
YAML
21 lines
832 B
YAML
name: codemention
|
|
on:
|
|
# pull_request_target is required so fork PRs get a write token to post the
|
|
# mention comment. Safe because there is no checkout — the action only reads
|
|
# PR metadata via the GitHub API; no fork code is fetched or executed.
|
|
pull_request_target:
|
|
types: [opened, synchronize, ready_for_review]
|
|
jobs:
|
|
codemention:
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
contents: read
|
|
pull-requests: write
|
|
steps:
|
|
# Pinned to a commit SHA (not a tag or branch) because this runs under
|
|
# pull_request_target with a write-scoped token — a re-pointed tag or
|
|
# moving branch would allow unreviewed upstream code to run here.
|
|
- uses: tobyhs/codemention@ebac5877393ab8693fd73b42708c8552043e9a3b # post-v1.5.2
|
|
with:
|
|
githubToken: ${{ secrets.GITHUB_TOKEN }}
|