Commit Graph
5 Commits
Author SHA1 Message Date
Noel Sabia 0a3c90cc74 fix(ci): create the release-please labels before the action runs
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m11s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 4s
PR Check / AI code review (opencode) (pull_request) Successful in 38s
release-please finds merged release PRs by the 'autorelease: pending'
label. Gitea resolves label names with GetLabelIDsInRepoByNames, a SQL IN
filter that silently drops unknown names, so on a repository without the
labels the PR is created unlabeled and every run finds zero merged release
PRs: no tag, no release, and the next release PR instead - with a green
run each time. That is what happened to #20 and #21.

The workflow now ensures both labels exist (idempotent: list, create the
missing ones) and gained workflow_dispatch so a missed release can be
replayed.
2026-10-24 20:21:50 +02:00
Noel Sabia a27bbbb2ab fix(ci): give release-please git credentials for the release-branch push
PR Check / Dependency audit (pull_request) Failing after 9s
PR Check / Dockerfile lint (droast) (pull_request) Failing after 4s
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 / AI code review (opencode) (pull_request) Successful in 28s
The 401 in run 89 was the final isomorphic-git push inside
code-suggester's createPullRequest, not an API call: tree, commit and
local ref update all ran through the token-authenticated octokit API,
then 'git push' used the git-username/git-password inputs - unset in
our workflow, so the push was anonymous. The remote branch
release-please--branches--main still sat at an old commit, proving the
push never landed. Pass the account name and the same token.
2026-10-18 19:41:33 +02:00
Noel Sabia e1192a2014 fix(ci): point release-please at PR_GITEA_TOKEN (write scopes)
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.
2026-10-18 18:28:41 +02:00
Noel Sabia 56ef59cbd6 ci: point release-please at config and manifest files
PR Check / Dockerfile lint (droast) (pull_request) Skipped
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 8s
PR Check / AI code review (opencode) (pull_request) Failing after 13s
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 34s
PR Check / Typecheck (pull_request) Successful in 38s
Replace the inline 'release-type: simple' with references to
release-please-config.json and .release-please-manifest.json so the
manifest-driven release strategy is used.
2026-10-18 16:48:04 +02:00
Noel Sabia 1d9da87986 ci: add PR checker workflow
Runs on every pull request:
- ESLint and vue-tsc typecheck
- gitleaks secret scan over full history
- pnpm dependency audit (advisory)
- droast Dockerfile lint (skips until a Dockerfile exists)
- Snyk dependency and base image scan
- opencode AI code review posted as PR comment
2026-10-18 15:16:12 +02:00