-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[registry] push fails due to security detection #65
Comments
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…to prevent that it cannot be pushed after merge
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…s updated regularly to prevent security issues
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…s updated regularly to prevent security issues (#67)
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…to prevent that it cannot be pushed after merge
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…n only update tags that are marked as latest
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…ush to prevent that the pipeline will break on tag creation (#66) * feat: [#65] Ensure that docker registry image is build on every push to prevent that it cannot be pushed after merge * fix: [#65] Update regitry image from 3.0.0-rc.2 to 3 as dependabot can only update tags that are marked as latest
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…ministration and use tag ref to prevent build breaks on tagging
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…ministration and use tag ref to prevent build breaks on tagging
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…ministration and use tag ref to prevent build breaks on tagging
sbp-bvanb
added a commit
that referenced
this issue
Mar 7, 2025
…ministration and use tag ref to prevent build breaks on tagging (#69)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It should be built on push as currently if tagged then a security pipeline will fail, by always running the build then "bump into failing pipeline due to security issue" can be avoided.
.github/workflows/mcvs-registry.yml
The text was updated successfully, but these errors were encountered: