fix: arm64 base digest #39

Merged
Noel merged 3 commits from fix/arm64-base-digest into main 2026-10-31 20:19:15 +00:00
Owner
No description provided.
Noel added 2 commits 2026-10-31 20:10:44 +00:00
The previous pin was the linux/amd64 platform manifest, so the arm64
runner failed instantly with 'no matching manifest for linux/arm64'.
Pin the OCI index digest that contains amd64 and arm64/v8.
ci(publish): add a manual build-only rehearsal trigger
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m10s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
3614bfd3ae
workflow_dispatch with version/push/latest inputs: push defaults to
false, so the runner, socket and registry login can be verified without
creating a tag or a package version. latest is never moved unless asked.

Failed to update PR description

Failed to update PR description

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Possible Issue

On a manual workflow_dispatch run, the workflow checks out the branch the run was started from, but the image is tagged with the version input (e.g. v1.5.0). If the operator runs the workflow from main (or any branch that is not the tag's commit) with push=true, the published ${IMAGE}:${VERSION} tag will contain the branch's code, not the code that the release tag points to. The immutability guard only protects against overwriting an already-published version, not against publishing a version that was never tagged. Consider checking out refs/tags/${{ inputs.version }} for manual runs, or at least verifying the tag exists and matches the checked-out commit before pushing.

version="$INPUT_VERSION"
if [ -z "$version" ]; then
  version="${GITHUB_REF_NAME:-$(git describe --tags --exact-match HEAD)}"
fi
## PR Reviewer Guide 🔍 <!-- pr-agent:review:full --> Here are some key observations to aid the review process: <table> <tr><td>⏱️&nbsp;<strong>Estimated effort to review</strong>: 3 🔵🔵🔵⚪⚪</td></tr> <tr><td>🧪&nbsp;<strong>No relevant tests</strong></td></tr> <tr><td>🔒&nbsp;<strong>No security concerns identified</strong></td></tr> <tr><td>⚡&nbsp;<strong>Recommended focus areas for review</strong><br><br> <details><summary><a href='https://git.noelsabia.dev/CV_Website/CV_Site_Nuxt/src/branch/fix/arm64-base-digest/.gitea/workflows/publish-image.yml#L102-L105'><strong>Possible Issue</strong></a> On a manual `workflow_dispatch` run, the workflow checks out the branch the run was started from, but the image is tagged with the `version` input (e.g. `v1.5.0`). If the operator runs the workflow from `main` (or any branch that is not the tag's commit) with `push=true`, the published `${IMAGE}:${VERSION}` tag will contain the branch's code, not the code that the release tag points to. The immutability guard only protects against overwriting an already-published version, not against publishing a version that was never tagged. Consider checking out `refs/tags/${{ inputs.version }}` for manual runs, or at least verifying the tag exists and matches the checked-out commit before pushing. </summary> ```yaml version="$INPUT_VERSION" if [ -z "$version" ]; then version="${GITHUB_REF_NAME:-$(git describe --tags --exact-match HEAD)}" fi ``` </details> </td></tr> </table>
Noel added 1 commit 2026-10-31 20:15:52 +00:00
Merge remote-tracking branch 'origin/main' into fix/arm64-base-digest
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m6s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 4s
e3e0b8d28c
# Conflicts:
#	OKF_Nuxt/log.md
Noel merged commit f619e5cbec into main 2026-10-31 20:19:15 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: CV_Website/CV_Site_Nuxt#39