The tag job in main.yaml references
anothrNick/github-tag-action@4ed44965e0
which does not exist upstream: the runner fails with
Unable to resolve 4ed44965...: reference not found
##[error]reference not found
The first 12 chars match the real commit, the rest is fabricated - the
signature of a hand-rewritten YAML (commit 5e1827b re-added the step with a
bad SHA after 8b583cc had removed it). The correct commit for tag v1.75.0
is 4ed44965e0db8dab2b466a16da04aec3cc312fd8.
Impact: main.yaml has been red on every push to master since (runs 8197 and
8616: hadolint/test/build green, tag failed), so no release tag is created
and tag.yaml never runs -> no release build pushed to Docker Hub.
Verified against the upstream repo: tag 1.75.0 (and the v1 alias) both point
at 4ed44965e0db8dab2b466a16da04aec3cc312fd8.
hadolint 2.15.x - pulled in by hadolint-action v3.5.0 - adds DL3066
("Non-numeric user-id may not be resolvable by host system"). The
Dockerfile's `USER muser` trips it and the hadolint job exits 1 (hadolint
fails on info-level findings by default), turning the PR Checks pipeline
red on the Renovate bump PR.
muser was created without an explicit uid/gid, so its numeric identity
depended on busybox's auto-assignment. Both ids are now pinned at
1000:1000 - the values Alpine was already assigning - and USER uses the
numeric form, which is always resolvable by the host.
Verified with the upstream hadolint v2.15.1 binary: the previous
Dockerfile reports "Dockerfile:9 DL3066 info" and exits 1, the fixed one
lints clean and exits 0.
The hadolint-action v3.3.0 -> v3.5.0 bump is included here (all four
workflows, SHA 06be81ba) so that master ends up on v3.5.0 with a clean
lint - superseding Renovate PR #23.
sh 'docker login --username ${DOCKER_USER} --password ${DOCKER_PASS}'
sh 'docker push ${dockerImage}'
}
}
}
}
}
}
Reference in New Issue
Block a user
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.