Compare commits
10
Commits
v1.4.0
..
700b1030fc
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
700b1030fc | ||
|
|
5f7027bd86 | ||
|
|
efb73378e9 | ||
|
|
a8355d976b | ||
|
|
214ec46fed | ||
|
|
c332c195a9 | ||
|
|
a129e89aec | ||
|
|
2497d91cf7 | ||
|
|
9ecf504843 | ||
|
|
a2259df877 |
No files matched your search
@@ -18,8 +18,8 @@ concurrency:
|
||||
|
||||
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
|
||||
# organisation, so k3s pulls git.noelsabia.dev/cv_website/nuxt:<tag>.
|
||||
IMAGE: git.noelsabia.dev/cv_website/nuxt
|
||||
APP_DIR: .
|
||||
|
||||
jobs:
|
||||
@@ -125,7 +125,7 @@ jobs:
|
||||
[ -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
|
||||
| docker login git.noelsabia.dev -u "$REGISTRY_USERNAME" --password-stdin
|
||||
|
||||
- name: Refuse to overwrite a published version
|
||||
env:
|
||||
@@ -143,7 +143,7 @@ jobs:
|
||||
# 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}"
|
||||
url="https://git.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' \
|
||||
|
||||
@@ -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
|
||||
+2
-2
@@ -16,7 +16,7 @@
|
||||
# runner's arm64 and this workstation's x86_64.
|
||||
# syntax: no BuildKit-only features used, so the default frontend suffices.
|
||||
|
||||
FROM node:26-slim@sha256:d62f13676d530f7edf97782729df69713c8ccfe6631e7f62f9ccab65968719a8 AS build
|
||||
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65 AS build
|
||||
|
||||
# pnpm pinned to the same version as CI (pr-checker.yml pins major 11) and
|
||||
# the local toolchain (11.26.0). Installed via npm from the node image - no
|
||||
@@ -38,7 +38,7 @@ COPY . .
|
||||
RUN pnpm build
|
||||
|
||||
|
||||
FROM node:26-slim@sha256:d62f13676d530f7edf97782729df69713c8ccfe6631e7f62f9ccab65968719a8
|
||||
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65
|
||||
|
||||
# pnpm is NOT installed in the runtime image: nothing here runs pnpm.
|
||||
ENV NODE_ENV=production \
|
||||
|
||||
+1
-1
@@ -1,4 +1,4 @@
|
||||
FROM node:26-slim@sha256:d62f13676d530f7edf97782729df69713c8ccfe6631e7f62f9ccab65968719a8
|
||||
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65
|
||||
|
||||
# Node no longer bundles pnpm (corepack and pnpm are both absent from this
|
||||
# image), so install it. First instruction, so later changes reuse the layer.
|
||||
|
||||
@@ -5,7 +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.
|
||||
* [Publishing images to the own registry](registry-publishing.md) - A release tag builds and pushes to git.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.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
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.
|
||||
description: A release tag builds the production image and pushes it to git.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 }
|
||||
@@ -20,13 +20,36 @@ sources:
|
||||
|
||||
# Decision
|
||||
|
||||
**The registry is Gitea's own, served on the Gitea host.** Gitea ships a
|
||||
built-in container registry per owner/organisation
|
||||
([docs.gitea.com - container](https://docs.gitea.com/usage/packages/container/)).
|
||||
The endpoint is the Gitea hostname itself - `git.noelsabia.dev` - and the
|
||||
`/cv_website/` path segment is the Gitea organisation; images live under
|
||||
the package of the repository that pushed them:
|
||||
|
||||
```
|
||||
docker login git.noelsabia.dev
|
||||
git.noelsabia.dev/cv_website/nuxt:<tag>
|
||||
```
|
||||
|
||||
There is nothing to stand up and nothing to reinvent: no separate
|
||||
Registry/Harbor deployment, no extra hostname, no extra certificate.
|
||||
TLS and auth are the ones Gitea already serves. The publishing workflow
|
||||
exists only to automate pushes to this built-in registry.
|
||||
|
||||
**Corrected 2026-10-31:** `registry.noelsabia.dev` was a separate
|
||||
hostname set up before this was known. It is not needed and is being
|
||||
removed on the server side; this repository now uses
|
||||
`git.noelsabia.dev` everywhere. Any leftover `registry.noelsabia.dev`
|
||||
reference is a bug.
|
||||
|
||||
`.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
|
||||
git.noelsabia.dev/cv_website/nuxt:v1.2.3
|
||||
git.noelsabia.dev/cv_website/nuxt:sha-<12-char-sha>
|
||||
git.noelsabia.dev/cv_website/nuxt:latest # newest release only
|
||||
```
|
||||
|
||||
**Trigger is the release tag, not the main push.** release-please creates
|
||||
@@ -103,7 +126,7 @@ run.
|
||||
|
||||
| Gitea secret | Use |
|
||||
|---|---|
|
||||
| `REGISTRY_USERNAME` | basic-auth user for `docker login registry.noelsabia.dev` |
|
||||
| `REGISTRY_USERNAME` | basic-auth user for `docker login git.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
|
||||
@@ -117,7 +140,7 @@ appears in the process list or the log.
|
||||
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.
|
||||
5. `git.noelsabia.dev` answers over HTTPS.
|
||||
|
||||
# Guards in the workflow
|
||||
|
||||
@@ -153,7 +176,7 @@ appears in the process list or the log.
|
||||
* 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.
|
||||
* That `git.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.
|
||||
|
||||
@@ -70,32 +70,62 @@ 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.
|
||||
|
||||
# Recovering a release that was merged without a label
|
||||
# The head branch must survive the merge (2026-10-27)
|
||||
|
||||
Labels exist only from the fixed workflow onwards. PRs merged before that
|
||||
still carry none, so tagging them is a one-time manual step:
|
||||
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):
|
||||
|
||||
```sh
|
||||
# add the pending label to the merged release PRs
|
||||
for n in 20 21; do
|
||||
curl -sS -X POST -H "Authorization: token $TOKEN" \
|
||||
-H 'Content-Type: application/json' \
|
||||
-d '{"labels":["autorelease: pending"]}' \
|
||||
"https://git.noelsabia.dev/api/v1/repos/CV_Website/CV_Site_Nuxt/issues/$n/labels"
|
||||
done
|
||||
```
|
||||
❯ Found pull request #22: 'chore: release main'
|
||||
✖ Bad branch name: refs/pull/22/head
|
||||
⚠ Expected 1 releases, only found 0
|
||||
```
|
||||
|
||||
Then run the release-please workflow again (it now has
|
||||
`workflow_dispatch`). It creates `v1.2.0` and `v1.3.0` from those PRs'
|
||||
bodies and replaces the label with `autorelease: tagged`.
|
||||
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
|
||||
|
||||
* 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.
|
||||
* That the release phase tags correctly once the label is present. The
|
||||
label path is now fixed at the source; the first recovery run proves it.
|
||||
|
||||
# Revisit when
|
||||
|
||||
|
||||
+1
-1
@@ -23,7 +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.
|
||||
* [Publishing images to the own registry](decisions/registry-publishing.md) - A release tag builds the image and pushes it to git.noelsabia.dev; the runner socket it needs is root-equivalent and belongs on a separate label.
|
||||
|
||||
## Docker and development environment
|
||||
|
||||
|
||||
+14
-1
@@ -1,12 +1,25 @@
|
||||
# Update Log
|
||||
|
||||
## 2026-10-31 (registry host corrected: Gitea's built-in registry on git.noelsabia.dev)
|
||||
|
||||
* **Correction**: `registry.noelsabia.dev` is gone from the documentation and the workflow. Gitea's built-in container registry is served on the Gitea hostname itself, so the image is **`git.noelsabia.dev/cv_website/nuxt:<tag>`** ([docs.gitea.com/usage/packages/container](https://docs.gitea.com/usage/packages/container/)). `registry.noelsabia.dev` was a separate hostname set up before that was known; the server-side setup is being reverted. No separate registry, no extra hostname, no extra certificate - Gitea already provides this by default.
|
||||
* **Update**: [publish-image.yml](../.gitea/workflows/publish-image.yml) - `IMAGE`, `docker login` and the v2 `manifests/<version>` immutability check all point at `git.noelsabia.dev`. [Publishing images to the own registry](decisions/registry-publishing.md) records the corrected host and the reason.
|
||||
|
||||
## 2026-10-31 (registry confirmed: Gitea's built-in container registry)
|
||||
|
||||
* **Confirmation**: Logged in and pushed by hand - push access works. The registry is **Gitea's built-in container registry** ([docs.gitea.com/usage/packages/container](https://docs.gitea.com/usage/packages/container/)), not a separately deployed component: it is served on the Gitea host, and the `/cv_website/` path segment is the organisation namespace. This is the default - no Registry/Harbor to stand up, nothing to reinvent. Host corrected in the entry above; see [Publishing images to the own registry](decisions/registry-publishing.md).
|
||||
|
||||
## 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`.
|
||||
* **Creation**: [publish-image.yml](../.gitea/workflows/publish-image.yml) - a `vX.Y.Z` tag push builds `Dockerfile` on the arm64 runner and pushes `git.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/`.
|
||||
|
||||
|
||||
+1
-1
@@ -20,7 +20,7 @@
|
||||
},
|
||||
"dependencies": {
|
||||
"@iconify-json/material-symbols": "^1.2.95",
|
||||
"@nuxt/icon": "2.6.0",
|
||||
"@nuxt/icon": "2.6.2",
|
||||
"@nuxtjs/i18n": "10.6.0",
|
||||
"@nuxtjs/seo": "6.0.1",
|
||||
"@nuxtjs/tailwindcss": "6.14.0",
|
||||
|
||||
@@ -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