Compare commits
33
Commits
v1.5.1
..
f56400a3f7
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
f56400a3f7 | ||
|
|
1cfa36f006 | ||
|
|
953fff2ce6 | ||
|
|
4d5ba1ecb1 | ||
|
|
aa89212003 | ||
|
|
0228e891cf | ||
|
|
fcbf203a85 | ||
|
|
96f4eacfae | ||
|
|
f0d45577e3 | ||
|
|
7572b4e5f6 | ||
|
|
d63360b980 | ||
|
|
a0192a6515 | ||
|
|
d76f2f54d1 | ||
|
|
068c6c41e8 | ||
|
|
f71a119f17 | ||
|
|
66cfdc1ec0 | ||
|
|
44f697f8f7 | ||
|
|
71107ad11e | ||
|
|
373dc4f677 | ||
|
|
52e05bab79 | ||
|
|
a89a19c809 | ||
|
|
023ee7fad2 | ||
|
|
2276b92268 | ||
|
|
ab20f54b86 | ||
|
|
a764a6b931 | ||
|
|
965f3bc03e | ||
|
|
466555f69c | ||
|
|
33655c034b | ||
|
|
c11a33fc1e | ||
|
|
f619e5cbec | ||
|
|
e3e0b8d28c | ||
|
|
3614bfd3ae | ||
|
|
7981575f86 |
No files matched your search
@@ -27,7 +27,7 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
container: node:22-bookworm
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- uses: actions/checkout@v7
|
||||
|
||||
- uses: pnpm/action-setup@v4
|
||||
with:
|
||||
@@ -55,7 +55,7 @@ jobs:
|
||||
# A cache outage must not turn into a red PR: install still works
|
||||
# without the store, just slower.
|
||||
continue-on-error: true
|
||||
uses: actions/cache@v4.1.0
|
||||
uses: actions/cache@v6.1.0
|
||||
with:
|
||||
path: ${{ steps.pnpm.outputs.store }}
|
||||
key: pnpm-store-${{ runner.os }}-${{ steps.pnpm.outputs.layout }}-${{ steps.pnpm.outputs.lockfile }}
|
||||
@@ -82,7 +82,7 @@ jobs:
|
||||
# breaks node-based actions like actions/checkout
|
||||
container: node:22-bookworm
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- uses: actions/checkout@v7
|
||||
with:
|
||||
fetch-depth: 0 # gitleaks scans the full history
|
||||
|
||||
@@ -110,7 +110,7 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
container: node:22-bookworm
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- uses: actions/checkout@v7
|
||||
|
||||
- uses: pnpm/action-setup@v4
|
||||
with:
|
||||
@@ -135,7 +135,7 @@ jobs:
|
||||
# binary in the multi-arch node image instead
|
||||
container: node:22-bookworm
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- uses: actions/checkout@v7
|
||||
|
||||
- name: Install droast
|
||||
run: |
|
||||
@@ -202,7 +202,7 @@ jobs:
|
||||
# so install the CLI via npm in the multi-arch node image instead
|
||||
container: node:22-bookworm
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- uses: actions/checkout@v7
|
||||
|
||||
- name: Install Snyk CLI
|
||||
run: npm install -g snyk@1 && snyk --version
|
||||
|
||||
@@ -9,6 +9,24 @@ on:
|
||||
push:
|
||||
tags:
|
||||
- 'v*'
|
||||
# Manual rehearsal from the Gitea UI (Actions -> Publish image -> Run
|
||||
# workflow). `push` defaults to false: the job builds and smoke-tests, then
|
||||
# stops without publishing, so the runner can be verified without creating
|
||||
# a tag or a package version. Set `push` to true (and `latest` only for a
|
||||
# real release) to publish.
|
||||
workflow_dispatch:
|
||||
inputs:
|
||||
version:
|
||||
description: 'Version to build, e.g. v0.0.1 (vMAJOR.MINOR.PATCH)'
|
||||
required: true
|
||||
push:
|
||||
description: 'Push the image to the registry'
|
||||
required: false
|
||||
default: 'false'
|
||||
latest:
|
||||
description: 'Also move :latest (real releases only)'
|
||||
required: false
|
||||
default: 'false'
|
||||
|
||||
# The runner has capacity 1, so releases already serialize. This keeps a
|
||||
# manual re-run from racing a fresh release on the same tags.
|
||||
@@ -41,7 +59,7 @@ jobs:
|
||||
# the CLI - see OKF_Nuxt/decisions/registry-publishing.md.
|
||||
container: node:22-bookworm
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- uses: actions/checkout@v7
|
||||
|
||||
- name: Install Docker CLI
|
||||
# Debian's docker.io, not a curl-piped binary from GitHub: apt is a
|
||||
@@ -72,10 +90,19 @@ jobs:
|
||||
|
||||
- name: Resolve version and tags
|
||||
id: version
|
||||
env:
|
||||
# Inputs go through env, not direct interpolation: a value pasted
|
||||
# into a `run:` block is shell code before any check can run.
|
||||
INPUT_VERSION: ${{ github.event.inputs.version }}
|
||||
INPUT_LATEST: ${{ github.event.inputs.latest }}
|
||||
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)}"
|
||||
# On a tag push GITHUB_REF_NAME is the tag; on workflow_dispatch it
|
||||
# is the BRANCH, so the manual version input must win. The git
|
||||
# fallback keeps tag pushes working if a runner omits the variable.
|
||||
version="$INPUT_VERSION"
|
||||
if [ -z "$version" ]; then
|
||||
version="${GITHUB_REF_NAME:-$(git describe --tags --exact-match HEAD)}"
|
||||
fi
|
||||
# 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
|
||||
@@ -91,7 +118,13 @@ jobs:
|
||||
# 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
|
||||
#
|
||||
# A manual run moves `latest` only when the `latest` input says so;
|
||||
# a rehearsal must never repoint the production tag.
|
||||
if [ "$INPUT_LATEST" = "true" ]; then
|
||||
latest=true
|
||||
echo "manual run requested :latest"
|
||||
elif 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
|
||||
@@ -128,6 +161,9 @@ jobs:
|
||||
| docker login git.noelsabia.dev -u "$REGISTRY_USERNAME" --password-stdin
|
||||
|
||||
- name: Refuse to overwrite a published version
|
||||
# Build-only rehearsals publish nothing, so an existing tag is not a
|
||||
# conflict there; the guard only protects actual pushes.
|
||||
if: ${{ github.event_name != 'workflow_dispatch' || github.event.inputs.push == 'true' }}
|
||||
env:
|
||||
REGISTRY_USERNAME: ${{ secrets.REGISTRY_USERNAME }}
|
||||
REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}
|
||||
@@ -213,6 +249,8 @@ jobs:
|
||||
run: docker tag "${IMAGE}:${VERSION}" "${IMAGE}:latest"
|
||||
|
||||
- name: Push image
|
||||
# Manual run with `push` left at false: build and smoke test only.
|
||||
if: ${{ github.event_name != 'workflow_dispatch' || github.event.inputs.push == 'true' }}
|
||||
env:
|
||||
VERSION: ${{ steps.version.outputs.version }}
|
||||
SHA: ${{ steps.version.outputs.sha }}
|
||||
@@ -228,3 +266,13 @@ jobs:
|
||||
else
|
||||
echo "Pushed ${IMAGE}:${VERSION}, :sha-${SHA} (:latest untouched)"
|
||||
fi
|
||||
|
||||
- name: Rehearsal summary
|
||||
if: ${{ github.event_name == 'workflow_dispatch' && github.event.inputs.push != 'true' }}
|
||||
env:
|
||||
VERSION: ${{ steps.version.outputs.version }}
|
||||
SHA: ${{ steps.version.outputs.sha }}
|
||||
run: |
|
||||
echo "Build-only rehearsal for ${VERSION} (${SHA}) - the image passed the smoke test and was NOT pushed."
|
||||
echo "Re-run with push=true to publish it."
|
||||
|
||||
@@ -21,7 +21,7 @@ jobs:
|
||||
# release-please action clones into its own temp directory and does not
|
||||
# check the workspace out, so without this step the job fails with
|
||||
# "Cannot find module .../scripts/reconcile-release-please.mjs".
|
||||
- uses: actions/checkout@v4
|
||||
- uses: actions/checkout@v7
|
||||
|
||||
# release-please marks its release PR with `autorelease: pending` and
|
||||
# later finds the merged PR by that label. Gitea's label API resolves
|
||||
|
||||
@@ -28,7 +28,7 @@ jobs:
|
||||
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
|
||||
container: renovate/renovate:44.216.4
|
||||
steps:
|
||||
- name: Run Renovate
|
||||
env:
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
{
|
||||
".": "1.5.1"
|
||||
".": "1.5.2"
|
||||
}
|
||||
@@ -1,5 +1,12 @@
|
||||
# Changelog
|
||||
|
||||
## [1.5.2](https://git.noelsabia.dev/CV_Website/CV_Site_Nuxt/compare/v1.5.1...v1.5.2) (2026-10-31)
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* **docker:** pin the multi-platform base image index digest ([7981575](https://git.noelsabia.dev/CV_Website/CV_Site_Nuxt/commit/7981575f862eb2c4d298327e21f7a006fec66591))
|
||||
|
||||
## [1.5.1](https://git.noelsabia.dev/CV_Website/CV_Site_Nuxt/compare/v1.5.0...v1.5.1) (2026-10-31)
|
||||
|
||||
|
||||
|
||||
+7
-4
@@ -12,11 +12,14 @@
|
||||
# edits invalidate almost nothing.
|
||||
#
|
||||
# Base image is digest-pinned to the same node:26-slim digest as the dev
|
||||
# container (OKF_Nuxt/decisions/dev-container-shape.md) - verified for the
|
||||
# runner's arm64 and this workstation's x86_64.
|
||||
# container (OKF_Nuxt/decisions/dev-container-shape.md). The digest is the
|
||||
# multi-platform OCI INDEX, not a platform manifest: the previous pin was
|
||||
# the linux/amd64 manifest digest, so `--platform linux/arm64` on the arm64
|
||||
# runner failed instantly with "no matching manifest for linux/arm64".
|
||||
# Index digest verified 2026-10-31 to contain linux/amd64 and linux/arm64/v8.
|
||||
# syntax: no BuildKit-only features used, so the default frontend suffices.
|
||||
|
||||
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65 AS build
|
||||
FROM node:26-slim@sha256:5adad64f9a1fca2d51972caa65983634c8a774eb300d72b20f7f2a0f60368072 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 +41,7 @@ COPY . .
|
||||
RUN pnpm build
|
||||
|
||||
|
||||
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65
|
||||
FROM node:26-slim@sha256:5adad64f9a1fca2d51972caa65983634c8a774eb300d72b20f7f2a0f60368072
|
||||
|
||||
# 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:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65
|
||||
FROM node:26-slim@sha256:5adad64f9a1fca2d51972caa65983634c8a774eb300d72b20f7f2a0f60368072
|
||||
|
||||
# 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.
|
||||
|
||||
@@ -34,6 +34,17 @@ the gateway must now **proxy to this server** instead of embedding
|
||||
`.output/public/`. That sibling decision needs updating; the compose wiring
|
||||
is still open.
|
||||
|
||||
# The arm64 digest lesson (2026-10-31)
|
||||
|
||||
The first real release (`v1.5.0`, `v1.5.1`) failed at `Build image` after one
|
||||
second: the pinned `sha256:18f03e4b...` was the **linux/amd64 platform
|
||||
manifest**, not the multi-platform index, so `docker build --platform
|
||||
linux/arm64` on the arm64 runner found no arm64 entry. The base is now
|
||||
pinned to the OCI **index** digest (`sha256:e4db4c91...`, contains
|
||||
linux/amd64 and linux/arm64/v8). Rule: a digest pin for a multi-arch image
|
||||
must be the index digest; `docker buildx imagetools inspect` prints both,
|
||||
and the platform manifests carry a `Platform:` line.
|
||||
|
||||
# Why `--ignore-scripts`
|
||||
|
||||
The `postinstall` script (`nuxt prepare`) runs before the source is copied
|
||||
|
||||
@@ -142,6 +142,25 @@ appears in the process list or the log.
|
||||
4. Namespace `cv` has an `imagePullSecret` for the same credentials.
|
||||
5. `git.noelsabia.dev` answers over HTTPS.
|
||||
|
||||
# Manual rehearsal (workflow_dispatch)
|
||||
|
||||
The workflow can be started from the Gitea UI (Actions → Publish image →
|
||||
Run workflow) without creating a tag:
|
||||
|
||||
| Input | Use |
|
||||
|---|---|
|
||||
| `version` | required, `vMAJOR.MINOR.PATCH` |
|
||||
| `push` | `false` (default) builds and smoke-tests only; `true` publishes |
|
||||
| `latest` | `false` unless this is a real release |
|
||||
|
||||
A build-only run publishes nothing, so it creates no package version and
|
||||
the immutability guard is skipped. This is the way to prove the runner,
|
||||
socket and registry login before the first release - a rehearsal must never
|
||||
move `latest`, which is why that input is explicit.
|
||||
|
||||
Gitea only offers the Run-workflow button for workflows present on the
|
||||
default branch, so this trigger is available once the change is on `main`.
|
||||
|
||||
# Guards in the workflow
|
||||
|
||||
| Guard | Why |
|
||||
|
||||
@@ -1,5 +1,10 @@
|
||||
# Update Log
|
||||
|
||||
## 2026-10-31 (first release builds failed: pinned the amd64 manifest)
|
||||
|
||||
* **Fix**: [Dockerfile](../Dockerfile) and [Dockerfile.dev](../Dockerfile.dev) - the base digest `sha256:18f03e4b...` was the **linux/amd64 platform manifest**, so `docker build --platform linux/arm64` on the arm64 runner failed at `Build image` one second after the step started (run 157, v1.5.1; run 153, v1.5.0). Both now pin the multi-platform OCI **index** digest `sha256:e4db4c91...`, verified with `docker buildx imagetools inspect` to contain linux/amd64 and linux/arm64/v8. See [Production image shape](decisions/production-image.md).
|
||||
* **Detail**: checkout, Docker CLI install, `Check daemon access`, registry login, the immutability guard and version resolution all passed - the runner and registry setup were correct; only the base image pin was wrong.
|
||||
|
||||
## 2026-10-31 (release-please tag: empty package-name is the verified fix)
|
||||
|
||||
* **Correction**: removing `package-name` in #36 was not enough. Run 183 shows the node strategy falling back to `package.json` `name`, so the release phase still failed with `PR component: undefined does not match configured component: nuxt-app`.
|
||||
@@ -54,6 +59,10 @@
|
||||
* **Creation**: `deploy/pr-agent/` (later removed; the service now lives in the Gitea compose stack) - compose service, example environment and operator README. The real `.env` lived only at `/home/noel/self-hosted/pr-agent/.env` (mode 600) on `server0`.
|
||||
* **State**: the container is running and the webhook signature path is verified. Gitea gained `[webhook] ALLOWED_HOST_LIST = private:3000` (one restart, healthy) and the repository has a signed webhook. The OpenCode Go API key was still missing at commit time, so no model call or real review has run yet.
|
||||
|
||||
## 2026-10-31 (manual publish rehearsal without a tag)
|
||||
|
||||
* **Creation**: [publish-image.yml](../.gitea/workflows/publish-image.yml) gained `workflow_dispatch` with `version`, `push` and `latest` inputs. Default is **build + smoke test only** (`push=false`): no tag, no package version, immutability guard skipped, `latest` never moved unless explicitly requested. Use it to verify the `publish` runner (socket + `automount`) before the first release. Manual runs do not replace the tag path - a published image still always maps to a release tag.
|
||||
|
||||
## 2026-10-31 (audit green again: nuxt 4.6.3 and dependency overrides)
|
||||
|
||||
* **Fix**: `pnpm audit --prod --audit-level moderate` failed on every branch (#30, #31, #33 and this PR) - new advisories plus a Nuxt patch release. `nuxt` 4.6.2 -> **4.6.3** clears GHSA-9v7c-q64q-vv33 (dot-segment middleware bypass), GHSA-3xf4-9g3c-4h4w and GHSA-x287-wcfc-q46c (dev-server file read/runtime config).
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "nuxt-app",
|
||||
"version": "1.5.1",
|
||||
"version": "1.5.2",
|
||||
"type": "module",
|
||||
"private": true,
|
||||
"engines": {
|
||||
|
||||
Generated
+653
-541
File diff suppressed because it is too large.
Load diff
+4
-4
@@ -26,23 +26,23 @@ overrides:
|
||||
# already in the tree via postcss-nesting and is API-compatible. Remove
|
||||
# the override when tailwindcss ships >= 7.1.6 itself (or the site moves
|
||||
# to Tailwind v4).
|
||||
postcss-selector-parser: 7.1.6
|
||||
postcss-selector-parser: 7.1.7
|
||||
# GHSA-f86p-h4j2-7qgj and GHSA-9wx9-5pv9-3349 (moderate, 2026-10-30):
|
||||
# seroval < 1.6.11 allows code/script injection through serialized output.
|
||||
# Nuxt's vite-builder still resolves 1.6.9; the patched 1.6.11 is the
|
||||
# smallest version that clears both advisories. Remove this when Nuxt ships
|
||||
# a vite-builder that resolves >= 1.6.11 itself.
|
||||
seroval: 1.6.11
|
||||
seroval: 1.7.9
|
||||
# GHSA-g3hv-75wg-m249 (moderate, 2026-10-31): minimatch < 11.0.1 has a
|
||||
# globparts amplification DoS. Deliberately NOT overridden - see the
|
||||
# auditConfig ignore note above.
|
||||
# GHSA-3g3m-2fjr-6pw4 (moderate, 2026-10-31): glob 9.0.0-14.0.1 bypasses
|
||||
# AbortSignal cancellation. Patched in 14.0.2; the range keeps glob 7 for
|
||||
# tailwind-config-viewer.
|
||||
"glob@>=9.0.0 <=14.0.1": 14.0.2
|
||||
"glob@>=9.0.0 <=14.0.1": 14.0.4
|
||||
# node-forge 1.4.1 shipped (2026-10-31) and clears every node-forge
|
||||
# advisory that was previously ignored - no ignore needed anymore.
|
||||
node-forge: 1.4.1
|
||||
node-forge: 1.4.3
|
||||
minimumReleaseAgeExclude:
|
||||
- '@rollup/rollup-darwin-x64@4.64.8'
|
||||
- '@rollup/rollup-freebsd-arm64@4.64.8'
|
||||
|
||||
Reference in new issue
Block a user