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.
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.
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.
## PR Reviewer Guide 🔍
<!-- pr-agent:review:full -->
Here are some key observations to aid the review process:
<table>
<tr><td>⏱️ <strong>Estimated effort to review</strong>: 3 🔵🔵🔵⚪⚪</td></tr>
<tr><td>🧪 <strong>No relevant tests</strong></td></tr>
<tr><td>🔒 <strong>No security concerns identified</strong></td></tr>
<tr><td>⚡ <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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Failed to update PR description
PR Reviewer Guide 🔍
Here are some key observations to aid the review process:
Possible Issue
On a manual
workflow_dispatchrun, the workflow checks out the branch the run was started from, but the image is tagged with theversioninput (e.g.v1.5.0). If the operator runs the workflow frommain(or any branch that is not the tag's commit) withpush=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 outrefs/tags/${{ inputs.version }}for manual runs, or at least verifying the tag exists and matches the checked-out commit before pushing.