Repository navigation
fix(release): add format validation, route inputs.name through env var, remove -f flags - #63
Open
KacperMalachowski wants to merge 1 commit into
Conversation
…r, remove -f flags release.yaml had no validation of inputs.name and used it unquoted in git tag/push with -f (force) flags. BOT_TOKEN was live in the runner environment during execution. - Add format validation step (x.y.z regex) before checkout - Route github.event.inputs.name through env: RELEASE_NAME - Remove -f from git tag and git push Refs kyma/oci-image-builder#618
KacperMalachowski
requested a deployment
to
restricted
September 30, 2026 08:04 — with
GitHub Actions
Waiting
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
release.yamlhad no validation ofinputs.nameand used it unquoted ingit tag/git pushwith-f(force) flags, whileBOT_TOKEN(contents: write) was live in the runner environment — the highest-risk caller identified in the security finding.Changes:
Validate release name formatstep that rejects any input not matching^[0-9]+\.[0-9]+\.[0-9]+$before checkoutgithub.event.inputs.namethroughenv: RELEASE_NAMEat the job level"$RELEASE_NAME"ingit tagandgit push-fflags fromgit tagandgit push origin(force-tagging without validation is unsafe)Refs kyma/oci-image-builder#618