Skip to content

ci: enforce lockfile and scope permissions in publish-e2e-cli - #1333

Open
sunitaprajapati89 wants to merge 1 commit into
masterfrom
fix/harden-test-yml
Open

sunitaprajapati89 wants to merge 1 commit into
masterfrom
fix/harden-test-yml

Conversation

@sunitaprajapati89

Copy link
Copy Markdown
Contributor

Switch the e2e-cli build to npm ci so the committed package-lock.json is enforced instead of silently drifting on push-to-master and the monthly cron run. Add a top-level read-only permissions block to drop the default write-scoped GITHUB_TOKEN.

Skipped build provenance attestation: it requires id-token and attestations write scopes, and nothing consumes the uploaded artifact today — e2e-tests.yml rebuilds e2e-cli from source.

Switch the e2e-cli build to `npm ci` so the committed
package-lock.json is enforced instead of silently drifting on
push-to-master and the monthly cron run. Add a top-level
read-only `permissions` block to drop the default write-scoped
GITHUB_TOKEN.

Skipped build provenance attestation: it requires id-token and
attestations write scopes, and nothing consumes the uploaded
artifact today — e2e-tests.yml rebuilds e2e-cli from source.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant