Compare commits
19
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
2497d91cf7 | ||
|
|
9ecf504843 | ||
|
|
a2259df877 | ||
|
|
0c937e6f80 | ||
|
|
e8ce629e1b | ||
|
|
f9ddbb7e1a | ||
|
|
0a3c90cc74 | ||
|
|
08eb042ad7 | ||
|
|
75f8a2c675 | ||
|
|
4e8aa28fd6 | ||
|
|
028b629152 | ||
|
|
67cf2328c6 | ||
|
|
ced3d8dab4 | ||
|
|
8150cd689f | ||
|
|
c3445ad55d | ||
|
|
eebd6ca697 | ||
|
|
435be63ae0 | ||
|
|
f3d3e196d0 | ||
|
|
c3cf1dfc47 |
No files matched your search
@@ -0,0 +1,230 @@
|
||||
name: Publish image
|
||||
|
||||
# Fires on the version tag release-please creates when the release PR is
|
||||
# merged (vX.Y.Z, plain tags - see OKF_Nuxt/decisions/release-engineering.md).
|
||||
# A push to main does NOT build: an image tag always maps to a released
|
||||
# version, so what runs in the cluster is traceable to a release, not to an
|
||||
# arbitrary commit.
|
||||
on:
|
||||
push:
|
||||
tags:
|
||||
- 'v*'
|
||||
|
||||
# The runner has capacity 1, so releases already serialize. This keeps a
|
||||
# manual re-run from racing a fresh release on the same tags.
|
||||
concurrency:
|
||||
group: publish-image
|
||||
cancel-in-progress: false
|
||||
|
||||
env:
|
||||
# Registry host + repository path. The path segment is the Gitea
|
||||
# organisation, so k3s pulls registry.noelsabia.dev/cv_website/nuxt:<tag>.
|
||||
IMAGE: registry.noelsabia.dev/cv_website/nuxt
|
||||
APP_DIR: .
|
||||
|
||||
jobs:
|
||||
publish:
|
||||
name: Build and push image
|
||||
# Dedicated label, NOT ubuntu-latest: this job needs the host Docker
|
||||
# socket, and `docker_host` is a runner-wide setting. Sharing a label
|
||||
# with pr-checker.yml would hand PR code (from a branch) a root-
|
||||
# equivalent socket on the host that also runs Gitea and k3s.
|
||||
# Register a second act_runner with `--labels publish:docker://node:22-bookworm`
|
||||
# and `container.docker_host: automount` in its config, before the first
|
||||
# tag: an unmatched label leaves the job queued indefinitely.
|
||||
runs-on: publish
|
||||
# A hung build would hold the capacity-1 runner and, through it, every
|
||||
# other job on this server. Gitea's instance default is not a contract.
|
||||
timeout-minutes: 20
|
||||
# Same base image as the other jobs. The build runs on the runner's
|
||||
# Docker daemon (not in a nested daemon), so this container only needs
|
||||
# the CLI - see OKF_Nuxt/decisions/registry-publishing.md.
|
||||
container: node:22-bookworm
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
|
||||
- name: Install Docker CLI
|
||||
# Debian's docker.io, not a curl-piped binary from GitHub: apt is a
|
||||
# signed channel, and bookworm ships an arm64 build. Only the client
|
||||
# is needed; the daemon lives on the host.
|
||||
run: |
|
||||
apt-get update
|
||||
apt-get install -y --no-install-recommends docker.io
|
||||
docker --version
|
||||
|
||||
- name: Check daemon access
|
||||
# Fail here, with the cause, instead of halfway through a build.
|
||||
# An unreachable daemon means the runner was started without the
|
||||
# host socket mounted: set `docker_host: automount` in the
|
||||
# act_runner config and restart the service.
|
||||
#
|
||||
# The socket is root-equivalent on the host, and automount is a
|
||||
# runner-wide setting - it applies to every job on that runner,
|
||||
# including PR jobs. Only enable it on a runner label that
|
||||
# PR-triggered jobs cannot use; see the trust boundary in
|
||||
# OKF_Nuxt/decisions/registry-publishing.md.
|
||||
run: |
|
||||
echo "DOCKER_HOST=${DOCKER_HOST:-<unset - the default socket path>}"
|
||||
if ! docker info > /dev/null 2>&1; then
|
||||
echo "::error::no Docker daemon reachable from this job - the act_runner needs the host Docker socket (docker_host: automount)"
|
||||
exit 1
|
||||
fi
|
||||
|
||||
- name: Resolve version and tags
|
||||
id: version
|
||||
run: |
|
||||
# GITHUB_REF_NAME is the tag on a tag push. The git fallback keeps
|
||||
# this working if a runner version does not set it.
|
||||
version="${GITHUB_REF_NAME:-$(git describe --tags --exact-match HEAD)}"
|
||||
# Strict semver, not a `v[0-9]*` prefix match: that would accept
|
||||
# `v1`, `v1-anything` and prereleases, all valid registry tags.
|
||||
if ! printf '%s' "$version" | grep -qE '^v[0-9]+\.[0-9]+\.[0-9]+$'; then
|
||||
echo "::error::expected a vMAJOR.MINOR.PATCH tag, got '${version}'"
|
||||
exit 1
|
||||
fi
|
||||
sha="$(git rev-parse --short=12 HEAD)"
|
||||
|
||||
# `latest` follows the newest release, not the newest build. A
|
||||
# re-run of an older tag (Gitea can replay any run) must not drag
|
||||
# `latest` backwards, while a re-run of the newest tag may set it:
|
||||
# that release had not produced an image yet.
|
||||
# A tag comparison needs the other tags, which a depth-1 tag
|
||||
# checkout does not have. If the fetch fails, skip `latest` and
|
||||
# say so - a wrong tag is worse than a missing one.
|
||||
if git fetch --tags --force --quiet origin 2>/dev/null; then
|
||||
newest="$(git tag -l | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -n 1)"
|
||||
if [ "$version" = "$newest" ]; then
|
||||
latest=true
|
||||
else
|
||||
latest=false
|
||||
echo "::warning::${version} is not the newest release (${newest}) - not moving :latest"
|
||||
fi
|
||||
else
|
||||
latest=false
|
||||
echo "::warning::could not list tags - not moving :latest"
|
||||
fi
|
||||
|
||||
# Short SHA tag alongside the version: OKF_CV_Website/architecture/
|
||||
# delivery.md asks for SHA-tagged images so every deploy is
|
||||
# traceable to a commit even after a tag is moved.
|
||||
{
|
||||
echo "version=${version}"
|
||||
echo "sha=${sha}"
|
||||
echo "latest=${latest}"
|
||||
} >> "$GITHUB_OUTPUT"
|
||||
echo "Building ${version} from ${sha} (latest: ${latest})"
|
||||
|
||||
- name: Log in to the registry
|
||||
env:
|
||||
REGISTRY_USERNAME: ${{ secrets.REGISTRY_USERNAME }}
|
||||
REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}
|
||||
run: |
|
||||
# Missing secrets must fail loudly: an anonymous `docker push`
|
||||
# would answer 401 with a message most people misread as a
|
||||
# missing repository.
|
||||
[ -n "$REGISTRY_USERNAME" ] || { echo "::error::secret REGISTRY_USERNAME is empty"; exit 1; }
|
||||
[ -n "$REGISTRY_PASSWORD" ] || { echo "::error::secret REGISTRY_PASSWORD is empty"; exit 1; }
|
||||
printf '%s' "$REGISTRY_PASSWORD" \
|
||||
| docker login registry.noelsabia.dev -u "$REGISTRY_USERNAME" --password-stdin
|
||||
|
||||
- name: Refuse to overwrite a published version
|
||||
env:
|
||||
REGISTRY_USERNAME: ${{ secrets.REGISTRY_USERNAME }}
|
||||
REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}
|
||||
VERSION: ${{ steps.version.outputs.version }}
|
||||
run: |
|
||||
# A version tag is immutable once published. Gitea can replay any
|
||||
# run, and `docker push` would silently replace :vX.Y.Z with a
|
||||
# rebuilt image, so the release would change content after the
|
||||
# fact. A missing tag (first attempt, or a run that failed before
|
||||
# pushing) is fine - nothing was published.
|
||||
#
|
||||
# Registry v2 API instead of `docker manifest inspect`: the
|
||||
# Debian 20.10 client fails that command on OCI indexes with
|
||||
# "unsupported manifest media type and no default available",
|
||||
# for existing and missing tags alike.
|
||||
url="https://registry.noelsabia.dev/v2/cv_website/nuxt/manifests/${VERSION}"
|
||||
code=$(curl -s -o /dev/null -w '%{http_code}' \
|
||||
-u "${REGISTRY_USERNAME}:${REGISTRY_PASSWORD}" \
|
||||
-H 'Accept: application/vnd.docker.distribution.manifest.v2+json' \
|
||||
-H 'Accept: application/vnd.oci.image.index.v1+json' \
|
||||
-H 'Accept: application/vnd.oci.image.manifest.v1+json' \
|
||||
"$url")
|
||||
echo "GET /v2/cv_website/nuxt/manifests/${VERSION}: HTTP ${code}"
|
||||
case "$code" in
|
||||
200) echo "::error::${VERSION} is already published and version tags are immutable - delete that tag in the registry deliberately to replace it"; exit 1 ;;
|
||||
404) echo "${VERSION} is not published yet - continuing" ;;
|
||||
401|403) echo "::error::registry rejected the credentials (HTTP ${code}) - check REGISTRY_USERNAME/REGISTRY_PASSWORD"; exit 1 ;;
|
||||
*) echo "::error::unexpected answer from the registry (HTTP ${code})"; exit 1 ;;
|
||||
esac
|
||||
|
||||
- name: Build image
|
||||
env:
|
||||
VERSION: ${{ steps.version.outputs.version }}
|
||||
SHA: ${{ steps.version.outputs.sha }}
|
||||
run: |
|
||||
# --platform is explicit so a build on the wrong architecture fails
|
||||
# instead of silently producing an amd64 image the arm64 node
|
||||
# cannot run. Native here, no QEMU involved.
|
||||
docker build \
|
||||
--platform linux/arm64 \
|
||||
--label "org.opencontainers.image.version=${VERSION}" \
|
||||
--label "org.opencontainers.image.revision=${SHA}" \
|
||||
-t "${IMAGE}:${VERSION}" \
|
||||
-t "${IMAGE}:sha-${SHA}" \
|
||||
"${APP_DIR}"
|
||||
|
||||
- name: Smoke-test the image
|
||||
env:
|
||||
VERSION: ${{ steps.version.outputs.version }}
|
||||
run: |
|
||||
# Start the real server inside the built image and require a 2xx
|
||||
# with a real SSR body, not an empty shell. Cheaper than
|
||||
# publishing a broken release, and the only step that proves the
|
||||
# Nitro output actually runs. Done inside the container because
|
||||
# the app's port is not reachable from this job container - the
|
||||
# daemon publishes on the host, not here.
|
||||
#
|
||||
# The size floor is deliberately loose: the rendered homepage was
|
||||
# 97 kB on 2026-10-24, so 10 kB catches "200 but nothing rendered"
|
||||
# without failing on a future copy change.
|
||||
docker run --rm "${IMAGE}:${VERSION}" sh -c '
|
||||
node .output/server/index.mjs &
|
||||
server=$!
|
||||
i=0
|
||||
while [ "$i" -lt 30 ]; do
|
||||
if out=$(node -e "fetch(\"http://127.0.0.1:3000/\").then(async r => { const body = await r.text(); if (!r.ok || body.length < 10000) process.exit(1); console.log(r.status + \" \" + body.length + \" bytes\") }).catch(() => process.exit(1))" 2>/dev/null); then
|
||||
echo "homepage rendered after ${i}s: HTTP ${out}"
|
||||
kill "$server"
|
||||
exit 0
|
||||
fi
|
||||
i=$((i + 1))
|
||||
sleep 1
|
||||
done
|
||||
echo "no 2xx homepage with a rendered body within 30s"
|
||||
kill "$server"
|
||||
exit 1
|
||||
'
|
||||
|
||||
- name: Tag latest
|
||||
if: steps.version.outputs.latest == 'true'
|
||||
env:
|
||||
VERSION: ${{ steps.version.outputs.version }}
|
||||
run: docker tag "${IMAGE}:${VERSION}" "${IMAGE}:latest"
|
||||
|
||||
- name: Push image
|
||||
env:
|
||||
VERSION: ${{ steps.version.outputs.version }}
|
||||
SHA: ${{ steps.version.outputs.sha }}
|
||||
LATEST: ${{ steps.version.outputs.latest }}
|
||||
run: |
|
||||
# Explicit per tag, not `--all-tags`: --all-tags would also push
|
||||
# stale local tags left on the shared daemon by earlier runs.
|
||||
docker push "${IMAGE}:${VERSION}"
|
||||
docker push "${IMAGE}:sha-${SHA}"
|
||||
if [ "$LATEST" = "true" ]; then
|
||||
docker push "${IMAGE}:latest"
|
||||
echo "Pushed ${IMAGE}:${VERSION}, :sha-${SHA}, :latest"
|
||||
else
|
||||
echo "Pushed ${IMAGE}:${VERSION}, :sha-${SHA} (:latest untouched)"
|
||||
fi
|
||||
@@ -2,6 +2,10 @@ on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
# Manual trigger so a missed release can be replayed without waiting for
|
||||
# the next push. The job is idempotent: it tags only merged release PRs
|
||||
# that carry the pending label.
|
||||
workflow_dispatch:
|
||||
|
||||
permissions:
|
||||
contents: write
|
||||
@@ -13,6 +17,38 @@ jobs:
|
||||
release-please:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
# release-please marks its release PR with `autorelease: pending` and
|
||||
# later finds the merged PR by that label. Gitea's label API resolves
|
||||
# names and *silently ignores unknown ones* (GetLabelIDsInRepoByNames
|
||||
# filters by name in SQL), so on a repository without these labels the
|
||||
# PR is created unlabeled, the release phase finds no merged release PR
|
||||
# and creates no tag - while the run still reports success. That is the
|
||||
# bug this step prevents: make the labels exist first, every run.
|
||||
- name: Ensure release-please labels exist
|
||||
env:
|
||||
GITEA_TOKEN: ${{ secrets.PR_GITEA_TOKEN }}
|
||||
run: |
|
||||
set -eu
|
||||
existing="$(curl -sS -H "Authorization: token ${GITEA_TOKEN}" \
|
||||
"${GITHUB_API_URL}/repos/${GITHUB_REPOSITORY}/labels?limit=50")"
|
||||
for name in "autorelease: pending" "autorelease: tagged"; do
|
||||
if printf '%s' "$existing" | grep -qF "\"name\":\"${name}\""; then
|
||||
echo "label exists: ${name}"
|
||||
continue
|
||||
fi
|
||||
code="$(curl -sS -o /tmp/label.json -w '%{http_code}' -X POST \
|
||||
-H "Authorization: token ${GITEA_TOKEN}" \
|
||||
-H 'Content-Type: application/json' \
|
||||
-d "{\"name\":\"${name}\",\"color\":\"ededed\",\"description\":\"release-please state\"}" \
|
||||
"${GITHUB_API_URL}/repos/${GITHUB_REPOSITORY}/labels")"
|
||||
if [ "$code" != "201" ]; then
|
||||
echo "::error::could not create label '${name}' (HTTP ${code})"
|
||||
cat /tmp/label.json
|
||||
exit 1
|
||||
fi
|
||||
echo "created label: ${name}"
|
||||
done
|
||||
|
||||
- uses: joaquinjsb/gitea-release-please-action@v4
|
||||
with:
|
||||
# One well-scoped token for all workflow API work (see
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
name: Renovate
|
||||
|
||||
# Renovate is not hosted for Gitea, so this repository runs it itself.
|
||||
# The bot opens dependency PRs through the API; the PR pipeline checks them
|
||||
# (a branch protection rule should require those checks before automerge).
|
||||
#
|
||||
# Manual setup: create a bot account with its full name and email set, give
|
||||
# it write access to this repository, and store a token with
|
||||
# repository read/write, issue read/write, user read and organization read
|
||||
# as the RENOVATE_TOKEN Actions secret.
|
||||
on:
|
||||
schedule:
|
||||
# Daily at 04:00 UTC. Gitea only schedules workflows that exist on the
|
||||
# default branch.
|
||||
- cron: "0 4 * * *"
|
||||
workflow_dispatch:
|
||||
|
||||
concurrency:
|
||||
group: renovate
|
||||
cancel-in-progress: false
|
||||
|
||||
jobs:
|
||||
renovate:
|
||||
name: Run Renovate
|
||||
runs-on: ubuntu-latest
|
||||
timeout-minutes: 30
|
||||
# Pinned and multi-arch (the runner is arm64). The image installs the
|
||||
# Node-based toolchain it needs on demand.
|
||||
container: renovate/renovate:44.198.2
|
||||
steps:
|
||||
- name: Run Renovate
|
||||
env:
|
||||
RENOVATE_PLATFORM: gitea
|
||||
# API root, not the web root. Renovate reads renovate.json from the
|
||||
# default branch through this endpoint.
|
||||
RENOVATE_ENDPOINT: https://git.noelsabia.dev/api/v1
|
||||
RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }}
|
||||
# This workflow lives in the repository it updates, so scope the bot
|
||||
# to it instead of every repository its account can see.
|
||||
RENOVATE_REPOSITORIES: CV_Website/CV_Site_Nuxt
|
||||
run: renovate
|
||||
@@ -0,0 +1,9 @@
|
||||
# actionlint configuration.
|
||||
#
|
||||
# `publish` is the label of the second act_runner registration (the one with
|
||||
# the host Docker socket). actionlint only knows GitHub's hosted labels, so
|
||||
# custom self-hosted labels have to be declared here or every workflow using
|
||||
# them fails the lint hook.
|
||||
self-hosted-runner:
|
||||
labels:
|
||||
- publish
|
||||
@@ -55,6 +55,12 @@ repos:
|
||||
hooks:
|
||||
- id: actionlint
|
||||
files: \.gitea/workflows/.*\.ya?ml$
|
||||
# actionlint only auto-loads its config when the file is
|
||||
# .github/actionlint.yaml *and* it recognises a project root by
|
||||
# .github/workflows, which this repo does not have (it uses
|
||||
# .gitea/workflows). Pass the config explicitly, or the custom
|
||||
# `publish` runner label is reported as unknown.
|
||||
args: [-config-file, .github/actionlint.yaml]
|
||||
|
||||
# --------------------------------------------------------- ESLint (Nuxt) -
|
||||
# Local hook: needs `pnpm install` to have run in this repo. --fix makes
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
{
|
||||
".": "1.1.0"
|
||||
".": "1.4.0"
|
||||
}
|
||||
+160
-1
@@ -1,6 +1,59 @@
|
||||
# Changelog
|
||||
|
||||
## [1.1.0](https://github.com/CV_Website/CV_Site_Nuxt/compare/v1.0.0...v1.1.0) (2026-10-23)
|
||||
## [1.4.0](https://github.com/CV_Website/CV_Site_Nuxt/compare/v1.3.0...v1.4.0) (2026-10-27)
|
||||
|
||||
|
||||
### Features
|
||||
|
||||
* add nuxt application shell ([5caa345](https://github.com/CV_Website/CV_Site_Nuxt/commit/5caa3457aa8f97dfca94059b15f8330e97bfb041))
|
||||
* added dockerignore, a development docker image and a qa/prod docker image ([1a78935](https://github.com/CV_Website/CV_Site_Nuxt/commit/1a78935c23ef2c756912d9f561a69569c2f45d2f))
|
||||
* extend ESLint config with default rule set ([e4ea5c3](https://github.com/CV_Website/CV_Site_Nuxt/commit/e4ea5c3e7c74c4d2c700ced71372da13e031eb6c))
|
||||
* **i18n:** add five locales and a header language switcher ([93ab0c0](https://github.com/CV_Website/CV_Site_Nuxt/commit/93ab0c0d79ac3de8f551d919798027f27bb819a8))
|
||||
* merged main into this branch ([cefdb34](https://github.com/CV_Website/CV_Site_Nuxt/commit/cefdb34d7ec33a176714388a4a0805177e8c4216))
|
||||
* pixel favicon and complete SEO metadata ([1c3503f](https://github.com/CV_Website/CV_Site_Nuxt/commit/1c3503fed0e6a385fcc98c5cfdcad605cf33e4be))
|
||||
* set up ESLint and typecheck with @nuxt/eslint ([4e2a03e](https://github.com/CV_Website/CV_Site_Nuxt/commit/4e2a03eab88495cbfa9db861919189da0c4b2889))
|
||||
* **ui:** build homepage hero, terminal and feature cards ([2673973](https://github.com/CV_Website/CV_Site_Nuxt/commit/26739731ed9e130c65d4530e067d82f17bc0534c))
|
||||
* **ui:** homepage shell with tailwind theme, self-hosted fonts, layout and header components ([8d53daa](https://github.com/CV_Website/CV_Site_Nuxt/commit/8d53daa4a6e4e9530ccad5c1ae25052e4a811849))
|
||||
* **ui:** mobile bottom nav on Nuxt Icon, footer hidden on phones ([3396c49](https://github.com/CV_Website/CV_Site_Nuxt/commit/3396c4949ec6f1a16957b6e004cae176126ad5f4))
|
||||
* **ui:** pixel-art breathing logo and external links ([7b5c97c](https://github.com/CV_Website/CV_Site_Nuxt/commit/7b5c97c84eab5f214c9e84ac79bd6e08642defa1))
|
||||
* **ui:** simplify terminal and contact bar on mobile ([47f4e64](https://github.com/CV_Website/CV_Site_Nuxt/commit/47f4e64f24c08e2d5b1e13c6f0bd938877b1d0c4))
|
||||
* **ui:** update homepage copy and import LinkedIn profile ([9a4d79a](https://github.com/CV_Website/CV_Site_Nuxt/commit/9a4d79a050c8d3a0d8bd43f9d473337b07c218b6))
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* **ci:** address AI review findings (credentials, supply chain) ([85f488a](https://github.com/CV_Website/CV_Site_Nuxt/commit/85f488a94dd8796ea5f11c292edddd32e21398cd))
|
||||
* **ci:** apply review findings round two ([a3e6aef](https://github.com/CV_Website/CV_Site_Nuxt/commit/a3e6aef901086f5f8b416e2aa7d29596517f9550))
|
||||
* **ci:** close the fail-open gate, enforce read-only sandbox ([3e68e63](https://github.com/CV_Website/CV_Site_Nuxt/commit/3e68e630dff92a7abd791b7a8808eb682f37a060))
|
||||
* **ci:** create the release-please labels before the action runs ([0a3c90c](https://github.com/CV_Website/CV_Site_Nuxt/commit/0a3c90cc7489b7657a9a142fb2b6248ae0738a63))
|
||||
* **ci:** deny write tools, never swallow review errors ([f8d1287](https://github.com/CV_Website/CV_Site_Nuxt/commit/f8d128705faa9493202cf724ae0a451d4dc6d1e5))
|
||||
* **ci:** gate the ai review to pull_request events, restore route announcer ([9be6298](https://github.com/CV_Website/CV_Site_Nuxt/commit/9be62982a4a2494351006463ae71bd99f4e49fe4))
|
||||
* **ci:** give release-please git credentials for the release-branch push ([a27bbbb](https://github.com/CV_Website/CV_Site_Nuxt/commit/a27bbbb2abf0fa8ddedd20c05bba2128e88faa3a))
|
||||
* **ci:** hand review diff to agent as file, not argv ([16b9291](https://github.com/CV_Website/CV_Site_Nuxt/commit/16b9291a5111b93d6e7da244f821589fa3432d87))
|
||||
* **ci:** harden the release publish workflow after the PR review ([435be63](https://github.com/CV_Website/CV_Site_Nuxt/commit/435be63ae0bd0fdac49e83f9ef5a21e9182efa16))
|
||||
* **ci:** install opencode v2 for the review job ([783c9cc](https://github.com/CV_Website/CV_Site_Nuxt/commit/783c9ccda369fe5ec05ea5085488998de125045c))
|
||||
* **ci:** JSON-encode review with node instead of jq ([a061fad](https://github.com/CV_Website/CV_Site_Nuxt/commit/a061fad9b1933414faa7e6a26bd3182c0ce6c9d7))
|
||||
* **ci:** make droast job actually run ([cf6f209](https://github.com/CV_Website/CV_Site_Nuxt/commit/cf6f209ebf03c3a4faf4e32971ba036d60ddb36b))
|
||||
* **ci:** pass --all-projects to snyk test ([7197f75](https://github.com/CV_Website/CV_Site_Nuxt/commit/7197f757a6447cf29a11f60914d89939bd647040))
|
||||
* **ci:** pick gitleaks binary by CPU architecture ([88dadd5](https://github.com/CV_Website/CV_Site_Nuxt/commit/88dadd584627e963b4dee719768644626e343488))
|
||||
* **ci:** point release-please at PR_GITEA_TOKEN (write scopes) ([e1192a2](https://github.com/CV_Website/CV_Site_Nuxt/commit/e1192a2014da8acfea37c5319f0b612f9f5a392e))
|
||||
* **ci:** publish on a dedicated runner label, immutable version tags ([eebd6ca](https://github.com/CV_Website/CV_Site_Nuxt/commit/eebd6ca69782f4e77b598078397c4e84881ce98d))
|
||||
* **ci:** pull gitleaks from GHCR and pin version ([ce9c090](https://github.com/CV_Website/CV_Site_Nuxt/commit/ce9c090a150e448919205f9386ff61bfe77dfdb9))
|
||||
* **ci:** run app jobs from repo root ([bb13f1a](https://github.com/CV_Website/CV_Site_Nuxt/commit/bb13f1a187d482b9bb55dafa303356114ece42ae))
|
||||
* **ci:** run gitleaks as binary in node image ([779cf20](https://github.com/CV_Website/CV_Site_Nuxt/commit/779cf20f45ec8db009065197140067a531649401))
|
||||
* **ci:** run Snyk CLI via npm on arm64 runner ([8d2a000](https://github.com/CV_Website/CV_Site_Nuxt/commit/8d2a00062e6381cbba9bdb703b210c8eb2201d92))
|
||||
* **ci:** switch review model to deepseek-v4.1-flash, pause snyk via workflow_dispatch ([9b0f89e](https://github.com/CV_Website/CV_Site_Nuxt/commit/9b0f89ef38c189905869567be513dbf72e694b2d))
|
||||
* **ci:** tell the reviewer the lockfile is excluded on purpose ([ad4e8d7](https://github.com/CV_Website/CV_Site_Nuxt/commit/ad4e8d7bd9e394d6c9f1b157f6cc71b28e62dcaa))
|
||||
* **ci:** use opencode-go plan model for AI review ([8b6bcb6](https://github.com/CV_Website/CV_Site_Nuxt/commit/8b6bcb6d70d123dda551f08ef2c05dc3d50733f2))
|
||||
* **ci:** use pnpm 11 in runner ([ecd0192](https://github.com/CV_Website/CV_Site_Nuxt/commit/ecd0192466f8d72b9f8532e32b1aea63ff9dd640))
|
||||
* **deps:** force patched postcss-selector-parser 7.1.6 (GHSA-rj75-hqrm-r3gf) ([9995fc7](https://github.com/CV_Website/CV_Site_Nuxt/commit/9995fc75ed521ab54af59498dab7afa33f01ac23))
|
||||
* **favicon:** keep the ICO transparent when BACKGROUND is null ([2f9f236](https://github.com/CV_Website/CV_Site_Nuxt/commit/2f9f236f13b318216784606901d008c8522bc65f))
|
||||
* **i18n:** keep root links in the active locale and fix switcher a11y ([e4b30ad](https://github.com/CV_Website/CV_Site_Nuxt/commit/e4b30ad9447e6117686a73b7b66a627d258a510d))
|
||||
* pass staged filenames to the eslint pre-commit hook ([81d658a](https://github.com/CV_Website/CV_Site_Nuxt/commit/81d658a87105434835016ae20b24ef3cb7617d86))
|
||||
* remove leftover merge conflict marker from pr-checker.yml ([8f36f14](https://github.com/CV_Website/CV_Site_Nuxt/commit/8f36f14720a4826fe4b4cebdf591994fa0961ae3))
|
||||
* unblock the release PR - real production image, reviewed audit ignores ([f32ad07](https://github.com/CV_Website/CV_Site_Nuxt/commit/f32ad076486127a1132b754eb8258105754355bb))
|
||||
|
||||
## [1.3.0](https://github.com/CV_Website/CV_Site_Nuxt/compare/v1.2.0...v1.3.0) (2026-10-24)
|
||||
|
||||
|
||||
### Features
|
||||
@@ -29,12 +82,118 @@
|
||||
* **ci:** gate the ai review to pull_request events, restore route announcer ([9be6298](https://github.com/CV_Website/CV_Site_Nuxt/commit/9be62982a4a2494351006463ae71bd99f4e49fe4))
|
||||
* **ci:** give release-please git credentials for the release-branch push ([a27bbbb](https://github.com/CV_Website/CV_Site_Nuxt/commit/a27bbbb2abf0fa8ddedd20c05bba2128e88faa3a))
|
||||
* **ci:** hand review diff to agent as file, not argv ([16b9291](https://github.com/CV_Website/CV_Site_Nuxt/commit/16b9291a5111b93d6e7da244f821589fa3432d87))
|
||||
* **ci:** harden the release publish workflow after the PR review ([435be63](https://github.com/CV_Website/CV_Site_Nuxt/commit/435be63ae0bd0fdac49e83f9ef5a21e9182efa16))
|
||||
* **ci:** install opencode v2 for the review job ([783c9cc](https://github.com/CV_Website/CV_Site_Nuxt/commit/783c9ccda369fe5ec05ea5085488998de125045c))
|
||||
* **ci:** JSON-encode review with node instead of jq ([a061fad](https://github.com/CV_Website/CV_Site_Nuxt/commit/a061fad9b1933414faa7e6a26bd3182c0ce6c9d7))
|
||||
* **ci:** make droast job actually run ([cf6f209](https://github.com/CV_Website/CV_Site_Nuxt/commit/cf6f209ebf03c3a4faf4e32971ba036d60ddb36b))
|
||||
* **ci:** pass --all-projects to snyk test ([7197f75](https://github.com/CV_Website/CV_Site_Nuxt/commit/7197f757a6447cf29a11f60914d89939bd647040))
|
||||
* **ci:** pick gitleaks binary by CPU architecture ([88dadd5](https://github.com/CV_Website/CV_Site_Nuxt/commit/88dadd584627e963b4dee719768644626e343488))
|
||||
* **ci:** point release-please at PR_GITEA_TOKEN (write scopes) ([e1192a2](https://github.com/CV_Website/CV_Site_Nuxt/commit/e1192a2014da8acfea37c5319f0b612f9f5a392e))
|
||||
* **ci:** publish on a dedicated runner label, immutable version tags ([eebd6ca](https://github.com/CV_Website/CV_Site_Nuxt/commit/eebd6ca69782f4e77b598078397c4e84881ce98d))
|
||||
* **ci:** pull gitleaks from GHCR and pin version ([ce9c090](https://github.com/CV_Website/CV_Site_Nuxt/commit/ce9c090a150e448919205f9386ff61bfe77dfdb9))
|
||||
* **ci:** run app jobs from repo root ([bb13f1a](https://github.com/CV_Website/CV_Site_Nuxt/commit/bb13f1a187d482b9bb55dafa303356114ece42ae))
|
||||
* **ci:** run gitleaks as binary in node image ([779cf20](https://github.com/CV_Website/CV_Site_Nuxt/commit/779cf20f45ec8db009065197140067a531649401))
|
||||
* **ci:** run Snyk CLI via npm on arm64 runner ([8d2a000](https://github.com/CV_Website/CV_Site_Nuxt/commit/8d2a00062e6381cbba9bdb703b210c8eb2201d92))
|
||||
* **ci:** switch review model to deepseek-v4.1-flash, pause snyk via workflow_dispatch ([9b0f89e](https://github.com/CV_Website/CV_Site_Nuxt/commit/9b0f89ef38c189905869567be513dbf72e694b2d))
|
||||
* **ci:** tell the reviewer the lockfile is excluded on purpose ([ad4e8d7](https://github.com/CV_Website/CV_Site_Nuxt/commit/ad4e8d7bd9e394d6c9f1b157f6cc71b28e62dcaa))
|
||||
* **ci:** use opencode-go plan model for AI review ([8b6bcb6](https://github.com/CV_Website/CV_Site_Nuxt/commit/8b6bcb6d70d123dda551f08ef2c05dc3d50733f2))
|
||||
* **ci:** use pnpm 11 in runner ([ecd0192](https://github.com/CV_Website/CV_Site_Nuxt/commit/ecd0192466f8d72b9f8532e32b1aea63ff9dd640))
|
||||
* **deps:** force patched postcss-selector-parser 7.1.6 (GHSA-rj75-hqrm-r3gf) ([9995fc7](https://github.com/CV_Website/CV_Site_Nuxt/commit/9995fc75ed521ab54af59498dab7afa33f01ac23))
|
||||
* **favicon:** keep the ICO transparent when BACKGROUND is null ([2f9f236](https://github.com/CV_Website/CV_Site_Nuxt/commit/2f9f236f13b318216784606901d008c8522bc65f))
|
||||
* **i18n:** keep root links in the active locale and fix switcher a11y ([e4b30ad](https://github.com/CV_Website/CV_Site_Nuxt/commit/e4b30ad9447e6117686a73b7b66a627d258a510d))
|
||||
* pass staged filenames to the eslint pre-commit hook ([81d658a](https://github.com/CV_Website/CV_Site_Nuxt/commit/81d658a87105434835016ae20b24ef3cb7617d86))
|
||||
* remove leftover merge conflict marker from pr-checker.yml ([8f36f14](https://github.com/CV_Website/CV_Site_Nuxt/commit/8f36f14720a4826fe4b4cebdf591994fa0961ae3))
|
||||
* unblock the release PR - real production image, reviewed audit ignores ([f32ad07](https://github.com/CV_Website/CV_Site_Nuxt/commit/f32ad076486127a1132b754eb8258105754355bb))
|
||||
|
||||
## [1.2.0](https://github.com/CV_Website/CV_Site_Nuxt/compare/v1.1.0...v1.2.0) (2026-10-24)
|
||||
|
||||
|
||||
### Features
|
||||
|
||||
* add nuxt application shell ([5caa345](https://github.com/CV_Website/CV_Site_Nuxt/commit/5caa3457aa8f97dfca94059b15f8330e97bfb041))
|
||||
* added dockerignore, a development docker image and a qa/prod docker image ([1a78935](https://github.com/CV_Website/CV_Site_Nuxt/commit/1a78935c23ef2c756912d9f561a69569c2f45d2f))
|
||||
* extend ESLint config with default rule set ([e4ea5c3](https://github.com/CV_Website/CV_Site_Nuxt/commit/e4ea5c3e7c74c4d2c700ced71372da13e031eb6c))
|
||||
* **i18n:** add five locales and a header language switcher ([93ab0c0](https://github.com/CV_Website/CV_Site_Nuxt/commit/93ab0c0d79ac3de8f551d919798027f27bb819a8))
|
||||
* merged main into this branch ([cefdb34](https://github.com/CV_Website/CV_Site_Nuxt/commit/cefdb34d7ec33a176714388a4a0805177e8c4216))
|
||||
* pixel favicon and complete SEO metadata ([1c3503f](https://github.com/CV_Website/CV_Site_Nuxt/commit/1c3503fed0e6a385fcc98c5cfdcad605cf33e4be))
|
||||
* set up ESLint and typecheck with @nuxt/eslint ([4e2a03e](https://github.com/CV_Website/CV_Site_Nuxt/commit/4e2a03eab88495cbfa9db861919189da0c4b2889))
|
||||
* **ui:** build homepage hero, terminal and feature cards ([2673973](https://github.com/CV_Website/CV_Site_Nuxt/commit/26739731ed9e130c65d4530e067d82f17bc0534c))
|
||||
* **ui:** homepage shell with tailwind theme, self-hosted fonts, layout and header components ([8d53daa](https://github.com/CV_Website/CV_Site_Nuxt/commit/8d53daa4a6e4e9530ccad5c1ae25052e4a811849))
|
||||
* **ui:** mobile bottom nav on Nuxt Icon, footer hidden on phones ([3396c49](https://github.com/CV_Website/CV_Site_Nuxt/commit/3396c4949ec6f1a16957b6e004cae176126ad5f4))
|
||||
* **ui:** pixel-art breathing logo and external links ([7b5c97c](https://github.com/CV_Website/CV_Site_Nuxt/commit/7b5c97c84eab5f214c9e84ac79bd6e08642defa1))
|
||||
* **ui:** simplify terminal and contact bar on mobile ([47f4e64](https://github.com/CV_Website/CV_Site_Nuxt/commit/47f4e64f24c08e2d5b1e13c6f0bd938877b1d0c4))
|
||||
* **ui:** update homepage copy and import LinkedIn profile ([9a4d79a](https://github.com/CV_Website/CV_Site_Nuxt/commit/9a4d79a050c8d3a0d8bd43f9d473337b07c218b6))
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* **ci:** address AI review findings (credentials, supply chain) ([85f488a](https://github.com/CV_Website/CV_Site_Nuxt/commit/85f488a94dd8796ea5f11c292edddd32e21398cd))
|
||||
* **ci:** apply review findings round two ([a3e6aef](https://github.com/CV_Website/CV_Site_Nuxt/commit/a3e6aef901086f5f8b416e2aa7d29596517f9550))
|
||||
* **ci:** close the fail-open gate, enforce read-only sandbox ([3e68e63](https://github.com/CV_Website/CV_Site_Nuxt/commit/3e68e630dff92a7abd791b7a8808eb682f37a060))
|
||||
* **ci:** deny write tools, never swallow review errors ([f8d1287](https://github.com/CV_Website/CV_Site_Nuxt/commit/f8d128705faa9493202cf724ae0a451d4dc6d1e5))
|
||||
* **ci:** gate the ai review to pull_request events, restore route announcer ([9be6298](https://github.com/CV_Website/CV_Site_Nuxt/commit/9be62982a4a2494351006463ae71bd99f4e49fe4))
|
||||
* **ci:** give release-please git credentials for the release-branch push ([a27bbbb](https://github.com/CV_Website/CV_Site_Nuxt/commit/a27bbbb2abf0fa8ddedd20c05bba2128e88faa3a))
|
||||
* **ci:** hand review diff to agent as file, not argv ([16b9291](https://github.com/CV_Website/CV_Site_Nuxt/commit/16b9291a5111b93d6e7da244f821589fa3432d87))
|
||||
* **ci:** harden the release publish workflow after the PR review ([435be63](https://github.com/CV_Website/CV_Site_Nuxt/commit/435be63ae0bd0fdac49e83f9ef5a21e9182efa16))
|
||||
* **ci:** install opencode v2 for the review job ([783c9cc](https://github.com/CV_Website/CV_Site_Nuxt/commit/783c9ccda369fe5ec05ea5085488998de125045c))
|
||||
* **ci:** JSON-encode review with node instead of jq ([a061fad](https://github.com/CV_Website/CV_Site_Nuxt/commit/a061fad9b1933414faa7e6a26bd3182c0ce6c9d7))
|
||||
* **ci:** make droast job actually run ([cf6f209](https://github.com/CV_Website/CV_Site_Nuxt/commit/cf6f209ebf03c3a4faf4e32971ba036d60ddb36b))
|
||||
* **ci:** pass --all-projects to snyk test ([7197f75](https://github.com/CV_Website/CV_Site_Nuxt/commit/7197f757a6447cf29a11f60914d89939bd647040))
|
||||
* **ci:** pick gitleaks binary by CPU architecture ([88dadd5](https://github.com/CV_Website/CV_Site_Nuxt/commit/88dadd584627e963b4dee719768644626e343488))
|
||||
* **ci:** point release-please at PR_GITEA_TOKEN (write scopes) ([e1192a2](https://github.com/CV_Website/CV_Site_Nuxt/commit/e1192a2014da8acfea37c5319f0b612f9f5a392e))
|
||||
* **ci:** publish on a dedicated runner label, immutable version tags ([eebd6ca](https://github.com/CV_Website/CV_Site_Nuxt/commit/eebd6ca69782f4e77b598078397c4e84881ce98d))
|
||||
* **ci:** pull gitleaks from GHCR and pin version ([ce9c090](https://github.com/CV_Website/CV_Site_Nuxt/commit/ce9c090a150e448919205f9386ff61bfe77dfdb9))
|
||||
* **ci:** run app jobs from repo root ([bb13f1a](https://github.com/CV_Website/CV_Site_Nuxt/commit/bb13f1a187d482b9bb55dafa303356114ece42ae))
|
||||
* **ci:** run gitleaks as binary in node image ([779cf20](https://github.com/CV_Website/CV_Site_Nuxt/commit/779cf20f45ec8db009065197140067a531649401))
|
||||
* **ci:** run Snyk CLI via npm on arm64 runner ([8d2a000](https://github.com/CV_Website/CV_Site_Nuxt/commit/8d2a00062e6381cbba9bdb703b210c8eb2201d92))
|
||||
* **ci:** switch review model to deepseek-v4.1-flash, pause snyk via workflow_dispatch ([9b0f89e](https://github.com/CV_Website/CV_Site_Nuxt/commit/9b0f89ef38c189905869567be513dbf72e694b2d))
|
||||
* **ci:** tell the reviewer the lockfile is excluded on purpose ([ad4e8d7](https://github.com/CV_Website/CV_Site_Nuxt/commit/ad4e8d7bd9e394d6c9f1b157f6cc71b28e62dcaa))
|
||||
* **ci:** use opencode-go plan model for AI review ([8b6bcb6](https://github.com/CV_Website/CV_Site_Nuxt/commit/8b6bcb6d70d123dda551f08ef2c05dc3d50733f2))
|
||||
* **ci:** use pnpm 11 in runner ([ecd0192](https://github.com/CV_Website/CV_Site_Nuxt/commit/ecd0192466f8d72b9f8532e32b1aea63ff9dd640))
|
||||
* **deps:** force patched postcss-selector-parser 7.1.6 (GHSA-rj75-hqrm-r3gf) ([9995fc7](https://github.com/CV_Website/CV_Site_Nuxt/commit/9995fc75ed521ab54af59498dab7afa33f01ac23))
|
||||
* **favicon:** keep the ICO transparent when BACKGROUND is null ([2f9f236](https://github.com/CV_Website/CV_Site_Nuxt/commit/2f9f236f13b318216784606901d008c8522bc65f))
|
||||
* **i18n:** keep root links in the active locale and fix switcher a11y ([e4b30ad](https://github.com/CV_Website/CV_Site_Nuxt/commit/e4b30ad9447e6117686a73b7b66a627d258a510d))
|
||||
* pass staged filenames to the eslint pre-commit hook ([81d658a](https://github.com/CV_Website/CV_Site_Nuxt/commit/81d658a87105434835016ae20b24ef3cb7617d86))
|
||||
* remove leftover merge conflict marker from pr-checker.yml ([8f36f14](https://github.com/CV_Website/CV_Site_Nuxt/commit/8f36f14720a4826fe4b4cebdf591994fa0961ae3))
|
||||
* unblock the release PR - real production image, reviewed audit ignores ([f32ad07](https://github.com/CV_Website/CV_Site_Nuxt/commit/f32ad076486127a1132b754eb8258105754355bb))
|
||||
|
||||
## [1.1.0](https://github.com/CV_Website/CV_Site_Nuxt/compare/v1.0.0...v1.1.0) (2026-10-24)
|
||||
|
||||
|
||||
### Features
|
||||
|
||||
* add nuxt application shell ([5caa345](https://github.com/CV_Website/CV_Site_Nuxt/commit/5caa3457aa8f97dfca94059b15f8330e97bfb041))
|
||||
* added dockerignore, a development docker image and a qa/prod docker image ([1a78935](https://github.com/CV_Website/CV_Site_Nuxt/commit/1a78935c23ef2c756912d9f561a69569c2f45d2f))
|
||||
* extend ESLint config with default rule set ([e4ea5c3](https://github.com/CV_Website/CV_Site_Nuxt/commit/e4ea5c3e7c74c4d2c700ced71372da13e031eb6c))
|
||||
* **i18n:** add five locales and a header language switcher ([93ab0c0](https://github.com/CV_Website/CV_Site_Nuxt/commit/93ab0c0d79ac3de8f551d919798027f27bb819a8))
|
||||
* merged main into this branch ([cefdb34](https://github.com/CV_Website/CV_Site_Nuxt/commit/cefdb34d7ec33a176714388a4a0805177e8c4216))
|
||||
* pixel favicon and complete SEO metadata ([1c3503f](https://github.com/CV_Website/CV_Site_Nuxt/commit/1c3503fed0e6a385fcc98c5cfdcad605cf33e4be))
|
||||
* set up ESLint and typecheck with @nuxt/eslint ([4e2a03e](https://github.com/CV_Website/CV_Site_Nuxt/commit/4e2a03eab88495cbfa9db861919189da0c4b2889))
|
||||
* **ui:** build homepage hero, terminal and feature cards ([2673973](https://github.com/CV_Website/CV_Site_Nuxt/commit/26739731ed9e130c65d4530e067d82f17bc0534c))
|
||||
* **ui:** homepage shell with tailwind theme, self-hosted fonts, layout and header components ([8d53daa](https://github.com/CV_Website/CV_Site_Nuxt/commit/8d53daa4a6e4e9530ccad5c1ae25052e4a811849))
|
||||
* **ui:** mobile bottom nav on Nuxt Icon, footer hidden on phones ([3396c49](https://github.com/CV_Website/CV_Site_Nuxt/commit/3396c4949ec6f1a16957b6e004cae176126ad5f4))
|
||||
* **ui:** pixel-art breathing logo and external links ([7b5c97c](https://github.com/CV_Website/CV_Site_Nuxt/commit/7b5c97c84eab5f214c9e84ac79bd6e08642defa1))
|
||||
* **ui:** simplify terminal and contact bar on mobile ([47f4e64](https://github.com/CV_Website/CV_Site_Nuxt/commit/47f4e64f24c08e2d5b1e13c6f0bd938877b1d0c4))
|
||||
* **ui:** update homepage copy and import LinkedIn profile ([9a4d79a](https://github.com/CV_Website/CV_Site_Nuxt/commit/9a4d79a050c8d3a0d8bd43f9d473337b07c218b6))
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* **ci:** address AI review findings (credentials, supply chain) ([85f488a](https://github.com/CV_Website/CV_Site_Nuxt/commit/85f488a94dd8796ea5f11c292edddd32e21398cd))
|
||||
* **ci:** apply review findings round two ([a3e6aef](https://github.com/CV_Website/CV_Site_Nuxt/commit/a3e6aef901086f5f8b416e2aa7d29596517f9550))
|
||||
* **ci:** close the fail-open gate, enforce read-only sandbox ([3e68e63](https://github.com/CV_Website/CV_Site_Nuxt/commit/3e68e630dff92a7abd791b7a8808eb682f37a060))
|
||||
* **ci:** deny write tools, never swallow review errors ([f8d1287](https://github.com/CV_Website/CV_Site_Nuxt/commit/f8d128705faa9493202cf724ae0a451d4dc6d1e5))
|
||||
* **ci:** gate the ai review to pull_request events, restore route announcer ([9be6298](https://github.com/CV_Website/CV_Site_Nuxt/commit/9be62982a4a2494351006463ae71bd99f4e49fe4))
|
||||
* **ci:** give release-please git credentials for the release-branch push ([a27bbbb](https://github.com/CV_Website/CV_Site_Nuxt/commit/a27bbbb2abf0fa8ddedd20c05bba2128e88faa3a))
|
||||
* **ci:** hand review diff to agent as file, not argv ([16b9291](https://github.com/CV_Website/CV_Site_Nuxt/commit/16b9291a5111b93d6e7da244f821589fa3432d87))
|
||||
* **ci:** harden the release publish workflow after the PR review ([435be63](https://github.com/CV_Website/CV_Site_Nuxt/commit/435be63ae0bd0fdac49e83f9ef5a21e9182efa16))
|
||||
* **ci:** install opencode v2 for the review job ([783c9cc](https://github.com/CV_Website/CV_Site_Nuxt/commit/783c9ccda369fe5ec05ea5085488998de125045c))
|
||||
* **ci:** JSON-encode review with node instead of jq ([a061fad](https://github.com/CV_Website/CV_Site_Nuxt/commit/a061fad9b1933414faa7e6a26bd3182c0ce6c9d7))
|
||||
* **ci:** make droast job actually run ([cf6f209](https://github.com/CV_Website/CV_Site_Nuxt/commit/cf6f209ebf03c3a4faf4e32971ba036d60ddb36b))
|
||||
* **ci:** pass --all-projects to snyk test ([7197f75](https://github.com/CV_Website/CV_Site_Nuxt/commit/7197f757a6447cf29a11f60914d89939bd647040))
|
||||
* **ci:** pick gitleaks binary by CPU architecture ([88dadd5](https://github.com/CV_Website/CV_Site_Nuxt/commit/88dadd584627e963b4dee719768644626e343488))
|
||||
* **ci:** point release-please at PR_GITEA_TOKEN (write scopes) ([e1192a2](https://github.com/CV_Website/CV_Site_Nuxt/commit/e1192a2014da8acfea37c5319f0b612f9f5a392e))
|
||||
* **ci:** publish on a dedicated runner label, immutable version tags ([eebd6ca](https://github.com/CV_Website/CV_Site_Nuxt/commit/eebd6ca69782f4e77b598078397c4e84881ce98d))
|
||||
* **ci:** pull gitleaks from GHCR and pin version ([ce9c090](https://github.com/CV_Website/CV_Site_Nuxt/commit/ce9c090a150e448919205f9386ff61bfe77dfdb9))
|
||||
* **ci:** run app jobs from repo root ([bb13f1a](https://github.com/CV_Website/CV_Site_Nuxt/commit/bb13f1a187d482b9bb55dafa303356114ece42ae))
|
||||
* **ci:** run gitleaks as binary in node image ([779cf20](https://github.com/CV_Website/CV_Site_Nuxt/commit/779cf20f45ec8db009065197140067a531649401))
|
||||
|
||||
@@ -5,6 +5,7 @@
|
||||
* [Vulnerability audit policy](vulnerability-audit-policy.md) - Blocking audit, reviewed ignore-list for unfixable advisories, and the pnpm-11 settings home.
|
||||
* [Release engineering](release-engineering.md) - release-please in manifest mode, conventional commits as input, message format enforced at commit time.
|
||||
* [Snyk paused and secrets policy](snyk-paused-and-secrets-policy.md) - Why the job is skipped rather than deleted, and the token scopes every workflow secret needs.
|
||||
* [Publishing images to the own registry](registry-publishing.md) - A release tag builds and pushes to registry.noelsabia.dev; main pushes do not build.
|
||||
* [Dev container shape](dev-container-shape.md) - The source is bind-mounted into a container that already holds the dependencies, and the dev server runs as the image's `node` user.
|
||||
* [Build layer order](build-layer-order.md) - Why the manifests are copied before the source, and what invalidates what.
|
||||
* [Build context filter](build-context-filter.md) - What `.dockerignore` may exclude, and the one thing it must never exclude.
|
||||
|
||||
@@ -0,0 +1,171 @@
|
||||
---
|
||||
type: Decision
|
||||
title: Publishing images to the own registry
|
||||
description: A release tag builds the production image and pushes it to registry.noelsabia.dev, because that is the only way Kubernetes can pull it.
|
||||
tags: [decision, ci, docker, registry, gitea-actions]
|
||||
status: draft
|
||||
generated: { by: opencode-go/deepseek-v4.1-flash, at: 2026-10-24T00:00:00Z }
|
||||
verified: { by: human:noel, at: not yet }
|
||||
sources:
|
||||
- id: workflow
|
||||
resource: .gitea/workflows/publish-image.yml
|
||||
title: Publish image workflow
|
||||
- id: dockerfile
|
||||
resource: Dockerfile
|
||||
title: Production Dockerfile
|
||||
- id: k8s
|
||||
resource: ../OKF_CV_Website/architecture/delivery.md
|
||||
title: Sibling bundle - image tags and registry pull
|
||||
---
|
||||
|
||||
# Decision
|
||||
|
||||
`.gitea/workflows/publish-image.yml` builds `Dockerfile` and pushes the
|
||||
result to the own registry:
|
||||
|
||||
```
|
||||
registry.noelsabia.dev/cv_website/nuxt:v1.2.3
|
||||
registry.noelsabia.dev/cv_website/nuxt:sha-<12-char-sha>
|
||||
registry.noelsabia.dev/cv_website/nuxt:latest # newest release only
|
||||
```
|
||||
|
||||
**Trigger is the release tag, not the main push.** release-please creates
|
||||
`vX.Y.Z` when the release PR is merged ([release
|
||||
engineering](release-engineering.md)); that tag push is the build. A main
|
||||
push would otherwise publish commits that no release describes, and
|
||||
`latest` would move on work in progress.
|
||||
|
||||
# Why not build on every main push
|
||||
|
||||
* The registry is the deployment channel. Every image in it should answer
|
||||
"which release is this", and a tagged commit does.
|
||||
* The runner has capacity 1 and shares 2 vCPU / 4 GB with Gitea and k3s
|
||||
(`OKF_CV_Website/architecture/server-budget.md`). A Nuxt image build can
|
||||
take over 1 GB; running it more often than a release buys nothing.
|
||||
* The PR checks already gate the code that becomes a release. A tag build
|
||||
is not the first time the tree is built - a failing build here is a
|
||||
packaging failure, not a surprise.
|
||||
|
||||
# Why docker-outside-of-docker
|
||||
|
||||
The job runs in `node:22-bookworm`, like every other job in this
|
||||
repository, and only needs the Docker client: `docker build` sends the
|
||||
build context over the socket, so the daemon never reads the container's
|
||||
filesystem. That requires the act_runner to mount its host socket:
|
||||
|
||||
```yaml
|
||||
# act_runner config.yaml
|
||||
container:
|
||||
docker_host: automount
|
||||
```
|
||||
|
||||
Without it the `Check daemon access` step fails first with a named cause
|
||||
instead of a mid-build error. The alternative - a privileged `docker:dind`
|
||||
sidecar - needs privileged mode and a second daemon per release; not worth
|
||||
it on this server.
|
||||
|
||||
## Trust boundary (the cost of the socket)
|
||||
|
||||
A mounted Docker socket is **root-equivalent on the host**: any job that
|
||||
has it can run `docker run -v /:/host` and read or write anything, which on
|
||||
this machine means Gitea's data, k3s, and the CV itself. `docker_host` is a
|
||||
**runner-wide** setting, so enabling it gives the socket to every job on
|
||||
that runner, including PR jobs whose code comes from a branch.
|
||||
|
||||
Therefore the rule: **the socket only ever goes on a runner label that
|
||||
PR-triggered jobs do not use.**
|
||||
|
||||
The workflow follows it by scheduling onto a dedicated label:
|
||||
|
||||
```yaml
|
||||
runs-on: publish # NOT ubuntu-latest, which pr-checker.yml uses
|
||||
```
|
||||
|
||||
That label only exists once a second act_runner registration is configured
|
||||
with `container.docker_host: automount` and, for example,
|
||||
`--labels publish:docker://node:22-bookworm`. Until then the job queues
|
||||
without starting, and `timeout-minutes` does not apply to a job that never
|
||||
starts - register the runner before the first release tag.
|
||||
|
||||
Not acceptable: adding `automount` to the shared `ubuntu-latest` runner.
|
||||
That hands PR code a root-equivalent socket on the host that also runs
|
||||
Gitea and k3s. If it is ever the only option, treat it as an accepted risk
|
||||
and record it here rather than letting the workflow imply it.
|
||||
|
||||
# Why `--platform linux/arm64`
|
||||
|
||||
The runner and the node are the same arm64 machine, so the build is native
|
||||
(no QEMU, no crossed dependencies). Stating the platform makes a build on
|
||||
another architecture fail instead of publishing an image the node cannot
|
||||
run.
|
||||
|
||||
# Secrets
|
||||
|
||||
| Gitea secret | Use |
|
||||
|---|---|
|
||||
| `REGISTRY_USERNAME` | basic-auth user for `docker login registry.noelsabia.dev` |
|
||||
| `REGISTRY_PASSWORD` | basic-auth password (or token) for the same login |
|
||||
|
||||
Both are repo secrets. The login uses `--password-stdin` so the value never
|
||||
appears in the process list or the log.
|
||||
|
||||
# Before the first release tag
|
||||
|
||||
1. Repo secrets `REGISTRY_USERNAME` and `REGISTRY_PASSWORD` exist.
|
||||
2. A runner with the `publish` label exists and its config has
|
||||
`container.docker_host: automount`. Without the label the job queues
|
||||
forever; without the socket it fails at `Check daemon access`.
|
||||
3. `pr-checker.yml` still runs on a label whose runner has no socket.
|
||||
4. Namespace `cv` has an `imagePullSecret` for the same credentials.
|
||||
5. `registry.noelsabia.dev` answers over HTTPS.
|
||||
|
||||
# Guards in the workflow
|
||||
|
||||
| Guard | Why |
|
||||
|---|---|
|
||||
| Strict `^vMAJOR.MINOR.PATCH$` check | A `v[0-9]*` prefix match accepts `v1`, `v1-anything` and `v1.2.3-rc1`, all of which are valid registry tags and would publish silently |
|
||||
| `latest` only when the built tag is the highest `vX.Y.Z` in the repository | Gitea can replay any run. Without the comparison, re-running `v1.2.0` after `v1.3.0` drags `latest` backwards. A re-run of the newest tag still moves it - that release had not produced an image yet. If the tag list cannot be fetched, `latest` is skipped with a warning rather than guessed |
|
||||
| A published version tag is never overwritten | Before building, the registry's v2 API is asked for `manifests/<version>`: `200` aborts the run, `404` continues. A replay of a released tag fails instead of silently replacing published content. `docker manifest inspect` is deliberately *not* used - the Debian 20.10 client fails it on OCI indexes with `unsupported manifest media type and no default available`, for existing and missing tags alike |
|
||||
| Smoke test before any push | The image is started and must answer 2xx with at least 10 kB of rendered HTML on `/` (the real page is ~97 kB), so "200 but nothing rendered" fails too. Port publishing is not usable here: the daemon binds on the host, not in the job container |
|
||||
| `timeout-minutes: 20` | A hung build would hold the capacity-1 runner and every job queued behind it |
|
||||
| `.github/actionlint.yaml` | Declares the custom `publish` label, otherwise the lint hook reports it as unknown. The hook passes the file with `-config-file`, because actionlint only auto-loads it when it recognises a `.github/workflows` project |
|
||||
|
||||
# Costs and consequences
|
||||
|
||||
* **Registry storage grows** by one image per release in three tags. The
|
||||
three tags share layers, so the extra cost is mostly the tag, not the
|
||||
bytes.
|
||||
* **Images accumulate on the runner's daemon** (`sha-`, version and
|
||||
`latest` tags). Pruning is not part of this change; add a
|
||||
`docker image prune` policy when the disk usage actually matters.
|
||||
* **`latest` is a convenience, not a pin.** Manifests should reference the
|
||||
version or SHA tag so a release rollback is a manifest edit.
|
||||
* **k3s needs pull credentials**: an `imagePullSecret` in the namespace for
|
||||
the same basic-auth pair, or `/etc/rancher/k3s/registries.yaml` if the
|
||||
registry is ever plain HTTP. Not part of this workflow.
|
||||
|
||||
# Not verified
|
||||
|
||||
* That the runner has the host socket mounted (`docker_host: automount`) -
|
||||
the workflow's first step answers this on the first release.
|
||||
* That the arm64 build succeeds: `Dockerfile` has been built on x86_64
|
||||
only ([production image](production-image.md)).
|
||||
* That the smoke test passes on arm64. The same script was run against an
|
||||
x86_64 build of the merged tree and answered 2xx; the arm64 run is the
|
||||
first release.
|
||||
* That `registry.noelsabia.dev` is reachable over HTTPS from the runner.
|
||||
A plain-HTTP endpoint fails `docker login` with `server gave HTTP
|
||||
response to HTTPS client` and needs `insecure-registries` on the daemon
|
||||
plus `registries.yaml` on k3s.
|
||||
* Whether Gitea runs a `pull_request` workflow from a fork without
|
||||
maintainer approval on this instance. That answer decides how severe the
|
||||
socket risk above really is.
|
||||
|
||||
# Revisit when
|
||||
|
||||
* A second image (the Go gateway or chapter service) needs publishing -
|
||||
then the workflow grows a matrix instead of being copied.
|
||||
* Deploys should follow automatically: the release workflow gains a
|
||||
`kubectl set image` step, or manifests start referencing the SHA tag.
|
||||
* Multi-arch becomes necessary (a laptop or a CI host of the other
|
||||
architecture pulls the image).
|
||||
@@ -48,10 +48,81 @@ feeds this machine is enforced locally by the commitizen pre-commit hook.
|
||||
3. Merge the release PR → version bumped, changelog written, tag
|
||||
`vX.Y.Z` created.
|
||||
|
||||
# The label is load-bearing (2026-10-24)
|
||||
|
||||
Steps 2 and 3 are connected by a label, not by the merge alone:
|
||||
|
||||
* release-please creates the release PR with `autorelease: pending`;
|
||||
* on the next run it lists merged PRs and keeps only those carrying that
|
||||
label; those are the releases it tags.
|
||||
|
||||
Gitea resolves label **names** in `POST /issues/{index}/labels` with
|
||||
`GetLabelIDsInRepoByNames`, which is a SQL `IN` filter: names that do not
|
||||
exist are dropped **without an error**. A repository with no labels
|
||||
therefore accepts the call, returns 200, and attaches nothing.
|
||||
|
||||
That is exactly what happened here: PRs #20 and #21 were merged as release
|
||||
PRs with no label at all, so every run found zero merged release PRs,
|
||||
created zero tags, and opened the next release PR instead — while reporting
|
||||
success. Three release PRs, no tags.
|
||||
|
||||
The workflow now creates both labels (`autorelease: pending`,
|
||||
`autorelease: tagged`) before the action runs. Idempotent: it reads the
|
||||
label list and creates only what is missing.
|
||||
|
||||
# The head branch must survive the merge (2026-10-27)
|
||||
|
||||
The label fix was necessary but not sufficient. PR #22 carried
|
||||
`autorelease: pending` when it was merged, and the run after it still
|
||||
created no tag. From its log (task 475):
|
||||
|
||||
```
|
||||
❯ Found pull request #22: 'chore: release main'
|
||||
✖ Bad branch name: refs/pull/22/head
|
||||
⚠ Expected 1 releases, only found 0
|
||||
```
|
||||
|
||||
Gitea rewrites a merged PR's `head.ref` to `refs/pull/<n>/head` once the
|
||||
head branch is deleted; the branch name survives only in `head.label`.
|
||||
The Gitea build of release-please reads `head.ref`
|
||||
(`BranchName.parse(mergedPullRequest.headBranchName)`, bundled at
|
||||
`dist/index.js:15288`) and abandons the release when it is not a release
|
||||
branch. GitHub keeps the branch name there, which is why the plugin's
|
||||
assumption holds on GitHub and not here.
|
||||
|
||||
The repository deleted the head branch of every merged PR
|
||||
(`default_delete_branch_after_merge: true`). It is `false` now, and a
|
||||
release PR must be merged with its branch kept. The mechanism was
|
||||
confirmed by comparison, not inference: while `fix/release_please` still
|
||||
existed, PR #23 reported `head.ref = fix/release_please`; every PR whose
|
||||
branch was gone reported `refs/pull/<n>/head`.
|
||||
|
||||
# Recovering the versions that never got a tag
|
||||
|
||||
The label alone cannot recover them — #20, #21 and #22 all lost their head
|
||||
branch, so release-please skips them for the reason above. Creating those
|
||||
tags is a one-time manual step:
|
||||
|
||||
| Version | Merge commit |
|
||||
|---|---|
|
||||
| `v1.1.0` | `67cf232` (#12) |
|
||||
| `v1.2.0` | `4e8aa28` (#20) |
|
||||
| `v1.3.0` | `08eb042` (#21) |
|
||||
| `v1.4.0` | `0c937e6` (#22) |
|
||||
|
||||
`v1.0.0` is the bootstrap changelog entry from the configuration commit
|
||||
`c89747e` (2026-10-18); no release PR produced it.
|
||||
|
||||
The manifest moved to 1.4.0 without any tag existing, so until a tag is
|
||||
present release-please has no baseline: it reported "No latest release
|
||||
found for path: ., component: , but a previous version (1.4.0) was
|
||||
specified in the manifest" and would compute the next release from the
|
||||
whole history.
|
||||
|
||||
# Not verified
|
||||
|
||||
* The first release PR end to end — needs at least one `feat:`/`fix:`
|
||||
commit on `main` after the workflow merge.
|
||||
* That the release phase tags correctly once the head branch survives a
|
||||
merge. The next release cycle proves it.
|
||||
* That `RELEASE_PLEASE_TOKEN_CV_SITE_NUXT` carries the `write:issue`
|
||||
scope the same way `PR_GITEA_TOKEN` needed it; the previous failure
|
||||
was an immediate API rejection consistent with a scope problem.
|
||||
@@ -62,3 +133,6 @@ feeds this machine is enforced locally by the commitizen pre-commit hook.
|
||||
`include-component-in-tag` and `separate-pull-requests` matter).
|
||||
* A release must trigger a deploy — the workflow gains a step after
|
||||
`release_created` is set.
|
||||
* The label step breaks: if Gitea ever starts rejecting unknown label
|
||||
names, the `Ensure release-please labels exist` step will fail loudly
|
||||
instead of silently, which is the point.
|
||||
@@ -23,6 +23,7 @@ config files — the configs say what, these documents say why.
|
||||
* [Vulnerability audit policy](decisions/vulnerability-audit-policy.md) - Blocking audit; reviewed ignore-list for unfixable advisories in pnpm-workspace.yaml.
|
||||
* [Release engineering](decisions/release-engineering.md) - release-please in manifest mode; conventional commits enforced at commit time.
|
||||
* [Snyk paused and secrets policy](decisions/snyk-paused-and-secrets-policy.md) - Quota-paused job kept in place; `write:issue` scope required on every workflow token.
|
||||
* [Publishing images to the own registry](decisions/registry-publishing.md) - A release tag builds the image and pushes it to registry.noelsabia.dev; the runner socket it needs is root-equivalent and belongs on a separate label.
|
||||
|
||||
## Docker and development environment
|
||||
|
||||
|
||||
@@ -1,5 +1,19 @@
|
||||
# Update Log
|
||||
|
||||
## 2026-10-27 (release-please still never tagged: the deleted head branch)
|
||||
|
||||
* **Fix**: [release-please-config.json](../release-please-config.json) gained `"changelog-host": "https://git.noelsabia.dev"` - the changelog compare links were generated against `github.com/CV_Website/CV_Site_Nuxt`, a host this repository does not live on. Root cause of the missing tags: **Gitea rewrites `head.ref` to `refs/pull/<n>/head` when the merged PR's branch is deleted**, and release-please parses that field as the release branch, so `BranchName.parse` fails and the release is dropped - silently, exit code 0. Evidence: run 143 (task 475) logs `✖ Bad branch name: refs/pull/22/head` right after `Found pull request #22`, then `Expected 1 releases, only found 0`; #22 did carry `autorelease: pending`. The repository deleted every merged branch (`default_delete_branch_after_merge: true`); it is `false` now. Four versions (1.1.0-1.4.0) were consumed by the manifest with no tag ever created, so the release baseline has to be restored by hand. See [Release engineering](decisions/release-engineering.md).
|
||||
|
||||
## 2026-10-24 (release-please never tagged: the missing labels)
|
||||
|
||||
* **Fix**: [release-please.yml](../.gitea/workflows/release-please.yml) - the workflow now creates `autorelease: pending` and `autorelease: tagged` before the action runs, and gained `workflow_dispatch` so a missed release can be replayed. Root cause: release-please finds merged release PRs **by label**, and Gitea resolves label names with `GetLabelIDsInRepoByNames`, a SQL `IN` filter that silently drops unknown names. The repository had no labels at all, so PRs #20 and #21 were merged unlabeled, every run found zero merged release PRs, created zero tags and opened the next release PR instead - reporting success each time. Evidence: run 137 green, 0 tags, 0 releases, `labels: []` on #20/#21/#22, and the repo's label list empty. See [Release engineering](decisions/release-engineering.md).
|
||||
|
||||
## 2026-10-24 (release publishes an image)
|
||||
|
||||
* **Creation**: [publish-image.yml](../.gitea/workflows/publish-image.yml) - a `vX.Y.Z` tag push builds `Dockerfile` on the arm64 runner and pushes `registry.noelsabia.dev/cv_website/nuxt` as the version and `sha-<12>`, plus `latest` when that tag is the newest release. Main pushes deliberately do not build: the registry holds releases, not commits. The job uses the runner's own Docker daemon (client only in the `node:22-bookworm` container), so the act_runner needs `container.docker_host: automount`; the first step fails with that cause if it is missing. That socket is root-equivalent, so it may only sit on a label PR jobs cannot use - recorded under the trust boundary in [Publishing images to the own registry](decisions/registry-publishing.md). Repo secrets: `REGISTRY_USERNAME`, `REGISTRY_PASSWORD`.
|
||||
* **Review follow-up** (PR #19, 1 BLOCKER + 4 WARN + 2 NIT): applied the strict `vMAJOR.MINOR.PATCH` check, the newest-release rule for `latest`, a smoke test that starts the image and requires 2xx on `/`, and `timeout-minutes: 20`. 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 built successfully over the socket).
|
||||
* **Second review follow-up** (PR #19): the job now runs on the dedicated `publish` label instead of `ubuntu-latest`, so the host socket it needs can never be shared with PR jobs - the earlier version required a runner configuration its own trust boundary forbade. Added the immutability guard (registry v2 `manifests/<version>`: `200` aborts, `404` continues) after measuring that `docker manifest inspect` fails on OCI indexes with the pinned 20.10 client; the smoke test now also requires a rendered body (10 kB floor) rather than a bare 2xx. `.github/actionlint.yaml` declares the custom label, and the hook passes it with `-config-file` because this repo keeps workflows in `.gitea/`.
|
||||
|
||||
## 2026-10-23 (profile data in the terminal)
|
||||
* **Creation**: [Profile data](profile.md) - imported the LinkedIn export `Profile.pdf` into `app/data/chapters.ts`: PreZero active; Defifort, Alignerr, Outlier, freelance and 42 finished. Each row carries a context label (Enterprise, Web3 startup, AI Developer, Freelance, Education). The terminal now shows 1 active / 5 sealed / 14 rebounds; the export has no entry for `dreambit`, `ongoing-studies` or `apprenticeship`, so those rows are gone. `uptime` and `rebounds` remain mock.
|
||||
* **Update**: [backend endpoints](backend-endpoints.md) - examples and totals now match the real six-chapter list; the source frontmatter points at the export.
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "nuxt-app",
|
||||
"version": "1.1.0",
|
||||
"version": "1.4.0",
|
||||
"type": "module",
|
||||
"private": true,
|
||||
"engines": {
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
"release-type": "node",
|
||||
"include-component-in-tag": false,
|
||||
"separate-pull-requests": false,
|
||||
"changelog-host": "https://git.noelsabia.dev",
|
||||
"packages": {
|
||||
".": {
|
||||
"package-name": "CV_Site_Frontend",
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
{
|
||||
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
|
||||
"automerge": true
|
||||
}
|
||||
Reference in new issue
Block a user