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.