diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 3158a6e..54197cc 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -43,6 +43,15 @@ jobs: - uses: actions/checkout@v4 with: fetch-depth: 0 + # The release job declares `contents: write`, which overrides this repo's + # read-only default workflow permission -- so the checkout's default + # persisted credential is WRITE-scoped and stays live in .git/config + # through `npm ci` below. A compromised dependency lifecycle script + # could read it off disk and push. semantic-release authenticates its + # own pushes from GITHUB_TOKEN, so it does not need the persisted + # credential; `persist-credentials: false` is semantic-release's own + # documented GitHub Actions recipe. (CWE-250) + persist-credentials: false - name: Setup Node.js uses: actions/setup-node@v4 with: diff --git a/CHANGELOG.md b/CHANGELOG.md index 8d91fbe..ef58fac 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -24,6 +24,8 @@ Releases are cut automatically by semantic-release from conventional commits. ### Added +- **Release workflow no longer persists a write-scoped git credential across `npm ci`.** The release job declares `contents: write`, which overrides this repo's read-only default workflow permission, so `actions/checkout`'s default persisted credential was write-scoped and lived in `.git/config` through dependency install, build and test — readable by any compromised dependency lifecycle script. `persist-credentials: false` is semantic-release's own documented GitHub Actions recipe; it authenticates its pushes from `GITHUB_TOKEN` directly and never needed the persisted credential. (CWE-250) + - Initial SDK: `MailprotectorClient` with fifteen resource classes (`resellers`, `customers`, `domains`, `userGroups`, `users`, `managers`, `messages`, `allowBlockRules`, `configuration`, `logs`, `statements`, `emailRouting`,