PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 35s
PR Check / Typecheck (pull_request) Successful in 38s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Failing after 8s
PR Check / Dockerfile lint (droast) (pull_request) Failing after 5s
PR Check / AI code review (opencode) (pull_request) Successful in 1m23s
The dedicated RELEASE_PLEASE_TOKEN_CV_SITE_NUXT secret authenticated for reads but threw when creating the release PR (exit 1, releases_created false, no PR created): it lacks write:repository / write:issue. Use the proven PR_GITEA_TOKEN instead, per the one-well-scoped-token policy in OKF_Nuxt/decisions/snyk-paused-and-secrets-policy.md.
28 lines
876 B
YAML
28 lines
876 B
YAML
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
|
|
permissions:
|
|
contents: write
|
|
pull-requests: write
|
|
|
|
name: release-please
|
|
|
|
jobs:
|
|
release-please:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: joaquinjsb/gitea-release-please-action@v4
|
|
with:
|
|
# One well-scoped token for all workflow API work (see
|
|
# OKF_Nuxt/decisions/snyk-paused-and-secrets-policy.md). The
|
|
# dedicated RELEASE_PLEASE_TOKEN_CV_SITE_NUXT secret failed with
|
|
# exit 1: reads worked (createReleases completed) but creating
|
|
# the release PR threw - the token lacked the write:repository /
|
|
# write:issue scopes. PR_GITEA_TOKEN has both and is proven by
|
|
# the AI-review comment posting.
|
|
token: ${{ secrets.PR_GITEA_TOKEN }}
|
|
config-file: release-please-config.json
|
|
manifest-file: .release-please-manifest.json
|