workflow_dispatch with version/push/latest inputs: push defaults to
false, so the runner, socket and registry login can be verified without
creating a tag or a package version. latest is never moved unless asked.
The previous pin was the linux/amd64 platform manifest, so the arm64
runner failed instantly with 'no matching manifest for linux/arm64'.
Pin the OCI index digest that contains amd64 and arm64/v8.
Removing package-name in #36 was not enough: the node strategy falls back to package.json name 'nuxt-app', so run 183 still failed with 'PR component: undefined does not match configured component: nuxt-app'.
An empty package-name is not nullish, so getBranchComponent() stays empty and matches the legacy release-please--branches--main branch. Verified by running the action's bundled release-please locally against the live Gitea API with writes intercepted: it produced POST /releases with tag_name v1.5.0 at a80c9eb and swapped #35 to autorelease: tagged. The official default release-type:node mode was tested the same way and still fails for #35.
PR #35 merged with its branch kept, but the release phase logged 'PR component: undefined does not match configured component: CV_Site_Frontend' and returned before creating the tag. With include-component-in-tag false the strategy component and release body component are empty, while getBranchComponent still returns package-name. Remove package-name so both sides are empty; the changelog headings are already version-only.
Evidence: run 181 (task 578) after #35 merged. The next run should create v1.5.0 at a80c9eb and mark #35 autorelease: tagged.
The release-please job never had a checkout because the action clones into its own temp directory. The new reconcile step runs a file from the workspace, so the first post-merge run failed with MODULE_NOT_FOUND for scripts/reconcile-release-please.mjs. Add actions/checkout@v4 before the label/reconcile steps; the action still uses its own temp clone for the release branch.
Both PR-Agent findings were confirmed. A tag at the merge commit now counts only when it is exactly v<manifest version>; foreign CI or annotation tags are logged and ignored. Pending release PRs are fetched through the autorelease: pending label filter instead of paging every closed PR, so a concurrent close cannot shift a page and hide one.
Also fail loudly on a merged PR without merge_commit_sha or a manifest without a version, instead of producing vundefined.
Rebased on main after the separate audit fix (e0c69c1); the dependency overrides and lockfile changes from the earlier local commit were dropped. Verified on the rebased tree: lint, typecheck, build, the exact audit command, actionlint and a live dry run.
Bump nuxt to 4.6.3 and override node-forge 1.4.1 and glob 14.0.2.
minimatch stays a reviewed ignore: its patch drops makeRe, which
eslint-plugin-import-x imports.
Verified locally: lint, typecheck, build, and the exact audit command.
The registry endpoint is the Gitea hostname itself, not a separate
registry.noelsabia.dev host. Point IMAGE, docker login and the v2
manifests check at git.noelsabia.dev and record the correction.
Verified by logging in to registry.noelsabia.dev and pushing by hand.
The registry is Gitea's own, not a separately deployed component, so
there is nothing to stand up or reinvent.
Move the service and its env file into the Gitea stack, remove the separate deploy directory and the unused /opt operator-access scripts, and keep the operational guide in OKF_Nuxt/pr-agent.md.
Renovate fetches changelogs and release notes from github.com. Anonymous
requests are rate-limited, so the first run skipped them and printed the
"no github.com credentials" warning in the PR body.
RENOVATE_GITHUB_COM_TOKEN now comes from a repository secret. It is
independent of RENOVATE_TOKEN: any github.com account with read-only
access is enough, and no scopes are needed for public repositories.
OpenCode Go rejects requests without x-opencode-session, and LiteLLM needs the openai/ prefix on the fallback model. Supply the header through LITELLM__EXTRA_HEADERS, keep the prefixed fallback, and stop auto-running /improve so a PR gets one review plus /describe.
The merge of main updated package.json to @nuxt/icon 2.6.2 without the lockfile, so frozen installs aborted. Regenerate the lockfile and force seroval 1.6.11 for GHSA-f86p-h4j2-7qgj and GHSA-9wx9-5pv9-3349.
Run PR-Agent as a pinned webhook server on the Gitea Docker network and review on PR open plus slash commands. The per-PR opencode installer and verdict-posting step are removed.
The server-side .env stays outside the repository; deploy/pr-agent/ holds the compose definition and operator notes.
Gitea has no hosted Renovate, so the repository runs the official image
from a scheduled Gitea Actions workflow. The platform settings stay in the
workflow environment because Renovate accepts them only in the self-hosted
config, not in renovate.json.
renovate.json keeps the repository config minimal: schema plus
automerge=true, which also covers major updates. The bot account and the
RENOVATE_TOKEN secret are the remaining manual steps.
The generated CHANGELOG linked every release to
github.com/CV_Website/CV_Site_Nuxt, a host this repository does not live
on. release-please takes the compare host from the configuration, so it
is set now.
The decision record also gains the real reason no tag was ever created:
Gitea rewrites a merged PR's head.ref to refs/pull/<n>/head once the head
branch is deleted, and the Gitea build parses that field as the release
branch. BranchName.parse then fails and the release is dropped with a
logged error while the run still exits 0. The repository deleted every
merged branch; that default is off now, and the versions the manifest
already consumed have to be tagged by hand.
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.
The review's blocker was real: runs-on: ubuntu-latest is the label
pr-checker.yml uses, and the job needs a runner-wide Docker socket, so the
only working configuration violated the trust boundary in the decision
doc. The job now runs on a dedicated 'publish' label that only a second
act_runner registration (docker_host: automount) may carry.
Version tags are now immutable: before building, the registry v2 API is
asked for manifests/<version> and 200 aborts the run. docker manifest
inspect cannot do this job - the pinned Debian 20.10 client fails on OCI
indexes for existing and missing tags alike (measured).
Also: the smoke test requires a rendered body (10 kB floor) on top of the
2xx, .github/actionlint.yaml declares the custom label, and the actionlint
hook passes that config explicitly because this repo keeps workflows in
.gitea/workflows, where actionlint does not auto-discover it.
Applied the findings that held up against the code:
- strict vMAJOR.MINOR.PATCH guard; v[0-9]* accepted v1, v1-foo and
prereleases, all valid registry tags
- latest now follows the newest release, so replaying an older tag cannot
drag it backwards; skipped with a warning if the tag list is unavailable
- smoke test starts the built image and requires 2xx on / before pushing
- timeout-minutes: 20 on the job, so a hung build cannot hold the
capacity-1 runner indefinitely
- the decision doc records the socket's blast radius: root-equivalent,
runner-wide, only on a label PR jobs cannot use
Rejected with evidence: the .dockerignore leak (.env*, *.pem, .git are
excluded) and the Docker client/daemon API mismatch (20.10.24 client
against a 29.9.2 daemon builds over the socket).
Build Dockerfile on every v* tag push (created by release-please when the
release PR merges) and push registry.noelsabia.dev/cv_website/nuxt as the
version, sha-<12> and latest. Main pushes do not build: the registry holds
releases, not commits.
The job runs in node:22-bookworm and needs only the Docker client, so the
act_runner must expose its host socket (container.docker_host: automount);
a preflight step fails with that cause when it does not.
Conflicts:
- app/pages/index.vue: kept main's SEO setup (SITE, useSeoMeta,
titleTemplate) alongside the branch's chapters import.
- OKF_Nuxt/log.md: both sides prepended entries; kept the profile and
metrics entries above main's PR #16, SEO, favicon and icon entries.
Also takes main's @nuxtjs/seo and @nuxt/icon setup, favicon/OG assets,
site.config.mjs and the CI review changes. lint, typecheck and build pass
after a frozen-lockfile install.
Below lg the chapter rows show only the context badge and the status, so
the terminal no longer needs 760px on a phone; the desktop grid is
unchanged. The contact bar stacks the email full width and puts LinkedIn
and the location side by side.
Contact values truncate instead of forcing the bar wider. Also fixes the
"someone we pull" typo in the third feature card and lets the hero quote
use the wider column.
AppNav, AppLogo and AppBottomNav used NuxtLink to "/", which resolves to the English root under prefix_except_default; they now use NuxtLinkLocale and drop the hardcoded aria-current. Bottom-nav labels go through $t as well. The switcher's accessible name now contains the visible locale code, aria-haspopup is gone in favour of a plain disclosure with aria-controls, and Escape returns focus to the trigger.
Contact bar: Gmail, Heilbronn and a LinkedIn link; the phone chip is
removed. Hero: System Architect / Programmer, new pill and quote.
Feature cards: humility, learning and helpfulness instead of the
infrastructure copy.
Terminal: six chapters from the LinkedIn export (PreZero active;
Defifort, Alignerr, Outlier, freelance and 42 finished), each with a
context label. Rows use a fixed grid so names, context badges, status,
uptime and outcome line up vertically; the title bar has red/yellow/green
traffic lights and the footer pluralises its counters (1/5/14).
OKF: new profile data document for the export and chapter mapping;
backend endpoint examples and totals match the real rows.
Resolved: nuxt.config modules now carry @nuxt/icon and @nuxtjs/seo alongside @nuxtjs/i18n; package.json keeps both dependency sets; pnpm-lock.yaml regenerated. Also set i18n.baseUrl from site.config.mjs so sitemap alternates and future hreflang links are absolute.
Locale files in i18n/locales for en, de, es, it and pl; English stays at / and the others are prefixed. One flag dropdown after the GitHub link on desktop, logo plus the language button on phones. Nav, quick links and footer strings go through $t, and the footer line drops "self-healing on purpose".
The diff filter drops pnpm-lock.yaml to keep the patch small; the model read
that as an uncommitted lockfile and raised a BLOCKER on PR #16. Say so in the
prompt instead of widening the diff.
Compose pages/index.vue from the desktop homepage mockup: decorative
backdrop scoped to the hero but not clipped at its bottom edge, hero with
status pill, quote and contact chips with copy buttons, terminal panel fed
by a chapter array with derived counters, and the three feature cards.
Split into app/components/home/ (auto-imported with the Home* prefix) and
keep the chapter data in app/data/chapters.ts so GET /api/chapters can
replace the mockup values later.
- generate favicon.ico and favicon.svg from the header avatar; the sprite
moves to app/utils/avatar.js so component and generators share one source
- register @nuxtjs/seo with site and Person schema.org data from
site.config.mjs; canonical, robots, sitemap and llms.txt follow the routes
- title "Noel Sabia — <role>", summary_large_image, and no duplicate
"| Noel Sabia" suffix from SEO Utils
- add a committed 1200x630 OG card generated by pnpm og-image; the dynamic
OG renderer and skew protection stay off for the static deployment
- pin the Node version @nuxtjs/seo 6 requires and document the setup in the
OKF bundle
- decisions/icons-via-nuxt-icon.md: local collection, mode svg,
serverBundle collections empty, scanned client bundle; 3 icons, 1.23 kB
- linked from the bundle index and the decisions index, logged
- AppBottomNav: fixed bar below md with Overview, Life Map and Dev View
- default.vue mounts it and carries pb-16 md:pb-0 so the footer stays clear
- AppFooter is hidden below md, where the bar takes over
- icons come from @nuxt/icon (mode svg, scanned client bundle) with the
Material Symbols collection installed locally, replacing the webfont
- deletes the 3.9 MiB Material Symbols woff2 and its @font-face
- review model: opencode-go/claude-haiku-5-5#medium instead of
deepseek-v4.1-flash#max; flash has no medium variant
- merge lint and typecheck into one job with a single pnpm install
- cache the pnpm store and opencode binary via actions/cache@v4.1.0,
keyed on a sha256 of the lockfile (hashFiles is empty on this runner)
- update the decision records and log
The release PR (chore: release main) failed two checks, both verified
locally before pushing:
- droast: the empty production Dockerfile failed DF071 (no
instructions). The new Dockerfile is a runnable Node server (SSR):
multi-stage, manifests-first layers, digest-pinned node:26-slim (same
digest as the dev container), non-root uid 1000, node-fetch
HEALTHCHECK. Measured: docker build succeeds in-image, container
serves HTTP 200 and reports healthy; droast reports 0 errors.
- audit: two high advisories with NO patched release anywhere
(node-forge <=1.4.0 and braces <=3.0.3 are the newest npm versions;
both build-time-only paths under nitropack). Recorded as
auditConfig.ignoreGhsas in pnpm-workspace.yaml with the reason and
removal condition - the audit output still names what it skipped.
pnpm 11 ignores the pnpm field in package.json (caught locally via
the WARN before pushing); settings live in pnpm-workspace.yaml.
OKF_Nuxt: recorded the production-image and audit-policy decisions,
updated log, indexes and open questions.
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.
Validated from review comment 82 on this PR: the 'bash -c' wrapper
consumed the first staged filename as $0 and the command never
referenced $@, so eslint received zero file arguments and linted the
whole repo - --fix silently rewrote unstaged files and WIP lint errors
blocked unrelated commits. The entry now receives filenames directly
from pre-commit (empirically verified with an arg probe); documented
the re-stage loop for --fix and dropped the redundant 'types: [file]'
filter.
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.
Findings validated from review comments 71 and 75:
- [BLOCKER] the no-verdict branch exited \${EXIT_CODE:-1} which is 0
when opencode succeeded without a verdict - job went green and the
post step published non-review output. The else branch now exits 1
unconditionally, the verdict is anchored to the last five lines (the
prompt itself contains VERDICT lines), and the post step re-verifies
the contract before posting.
- [BLOCKER] the v1 'permission' object is ignored by the opencode v2
CLI - shell commands executed in both review runs despite deny. The
config now uses the v2 'permissions' array with 'shell' as the
action name, denying edit/shell/webfetch/websearch/external_directory.
- hygiene: droast linting prunes node_modules, audit comment names the
exact key to re-add, shell blocks verified with sh -n.
Four new decision documents covering the pipeline work: layering,
AI review setup (provider prefix, v2 CLI, env-only auth, verdict
gate), release engineering (release-please manifest mode), and the
Snyk pause with the token scope policy. Index grouped, log extended,
open questions updated.
- release-please-config.json: node release type, root package,
plain v-tags, default versioning
- .release-please-manifest.json: track current version (1.0.0)
- package.json: add version field required by the node release type
- release-please.yml: use the config/manifest files
- droast: chmod +x was lost in the checksum rewrite (would have
failed with exit 126); checksums now pinned in the workflow
instead of trust-on-first-use
- permission config migrated to the OpenCode v2 schema (permissions
array, bash renamed shell, websearch and external_directory denied)
- posting gate is now the output contract (verdict line present)
instead of the exit code: opencode can exit 1 on benign tool
denials after a completed review
- find -print -quit instead of piping into head (SIGPIPE, exit 141)
- audit comment now says to re-add continue-on-error
Merge origin/main (Dockerfile, Dockerfile.dev, .dockerignore) into
the release-please branch; resolve pr-checker.yml in favour of
opencode-go/deepseek-v4-pro#max.
- [BLOCKER] remove opencode.json from the checkout: it held the API
key in plaintext, readable by the review agent, and a malicious PR
diff could prompt-inject the agent into quoting it in the publicly
visible review comment. Env-only auth (verified headless). The
permission config moves to $HOME/.config/opencode - outside the
checkout and secret-free.
- [WARN] verify the droast binary against the publisher's
sha256sums.txt of the same pinned release
- [WARN] pin the opencode v2 installer to 2.0.32
Findings validated with the validate-pr-review skill; findings 4/5
are moot with the blocker fix.
- deny edit/bash/webfetch in the generated opencode.json: headless
permission prompts are the most likely cause of the review agent
working silently for minutes and then dying; denying write tools
also makes the reviewer provably read-only
- capture the exit code without triggering 'set -e' ('|| EXIT_CODE=$?')
so the captured output is always printed before failing - the
previous version aborted before 'cat' and produced silent failures
The classic installer (opencode.ai/install) ships only OpenCode 1.x
- v1.19.3 on arm64 - which cannot resolve model variants and failed
with ProviderModelNotFoundError for deepseek-v4-pro#max. Use the v2
installer (currently v2.0.32, same version as local dev); verified
working in a fresh arm64 container with key-only auth.
The dockerfile-lint job skipped on every PR despite Dockerfiles
existing: the act runner's hashFiles() evaluation returned empty.
Replace it with an explicit file-discovery step. Also run the droast
binary in node:22-bookworm (arch-aware install) instead of the
vendor image, which ships no node and would fail actions/checkout
with exit 127 - same failure mode as the gitleaks image.
The headless CI container has no stored credentials, so auth depends
entirely on the injected key. Generate an opencode.json at runtime
that binds OPENCODE_API_KEY to the opencode-go provider explicitly,
removing any dependence on env-var-to-provider mapping behavior.
- audit no longer runs with continue-on-error: a failed audit must
turn the pipeline red, not pass silently
- opencode review runs with --print-logs so auth and provider errors
(e.g. invalid API key vs missing Go subscription) appear in the job
log instead of an opaque exit 1
main changed the review model to the default thinking budget; keep
opencode-go/deepseek-v4-pro#max (plan-included, max effort) which
supersedes both earlier variants.
The 'opencode' provider prefix points at OpenCode Zen (pay-per-call,
no funds), which failed every review run with 'Insufficient account
funds'. The opencode-go $10 plan covers deepseek-v4-pro with high
and max variants - use opencode-go/deepseek-v4-pro#max.
The 'opencode' provider prefix points at OpenCode Zen (pay-per-call,
no funds). The opencode-go $10 plan covers deepseek-v4-pro with high
and max variants - use opencode-go/deepseek-v4-pro#max.
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.
- release-please-config.json: node release type, root package,
plain v-tags, default versioning (fix->patch, feat->minor,
BREAKING CHANGE->major)
- .release-please-manifest.json: track current version (1.0.0)
- package.json: add version field required by the node release type
#max exceeded the available opencode account funds; the default
thinking budget keeps the flagship model at lower cost. #max remains
available by re-adding the variant.
Passing the PR diff as a command-line argument exceeded
MAX_ARG_STRLEN (128KiB per single argument; the diff was 190KB,
mostly pnpm-lock.yaml). The shell failed with E2BIG ('Argument list
too long') and the tee pipeline masked the failure, so the raw error
log got posted as a 'review' comment.
- exclude pnpm-lock.yaml from the review diff (pnpm audit covers deps)
- write the diff to .pr-review-diff.patch in the workspace; the agent
reads it with file tools
- redirect output instead of piping through tee and fail the job when
opencode fails, so errors are never posted as review comments
- model: opencode/deepseek-v4-pro#max (requires funds on the opencode
account; flash fallback documented in a comment)
- review prompt rewritten: SSR/hydration/reactivity pitfalls, Nuxt
server-route security, runtime config leaks, Go error handling,
concurrency and resource hygiene, frontend/backend contract checks
- strict output format with [BLOCKER]/[WARN]/[NIT] severities mapped
to the approve/request-changes verdict
- Snyk job disabled via 'if: false': free plan only has ~100 test
credits/month and the job runs 2 tests per PR push
- PR comment step no longer fails silently: curl prints the HTTP
status and response body, making token/URL errors visible
Dockerfile linting is already covered by the droast job; the second
Snyk step now scans our own source for code vulnerabilities (XSS,
injection, unsafe patterns) instead of the base image.
The pnpm-workspace.yaml makes Snyk treat the project as a package
workspace; without --all-projects it aborts with SNYK-CLI-0000
(422 Unprocessable Entity).
The snyk/snyk:node image is amd64-only and cannot start on an arm64
runner. Install the Snyk CLI through npm (supports linux/arm64) in
the multi-arch node:22-bookworm image instead.
Replace anthropic/claude-sonnet-4-5 with opencode/deepseek-v4-pro for
a large cost reduction while keeping thorough, high-effort reviews.
Documented cheaper fallback: deepseek-v4.1-flash(-free).
The gitleaks container image ships no node binary, so node-based
actions like actions/checkout fail with exit code 127. Install the
gitleaks v8.28.0 binary in the standard node:22-bookworm image
instead.
gitleaks is not published on Docker Hub, so the container image pull
failed with 'pull access denied'. Use ghcr.io/gitleaks/gitleaks and
pin v8.28.0 for reproducible scans.
pnpm 9 treats the config-only pnpm-workspace.yaml (allowBuilds, no
packages field) as a workspace definition and fails with 'packages
field missing or empty'. Pin the same major version as local dev.
The Gitea repo CV_Website/CV_Site_Nuxt checks out to a workspace that
already is the app root, so working-directory CV_Site_Nuxt resolved to
a doubled, non-existent path.
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