chore(ci): pin PR-title action to commit SHA and add Dependabot#78
Open
Gabrielpanga wants to merge 2 commits into
Open
chore(ci): pin PR-title action to commit SHA and add Dependabot#78Gabrielpanga wants to merge 2 commits into
Gabrielpanga wants to merge 2 commits into
Conversation
Pin amannn/action-semantic-pull-request to its full commit SHA (48f256284bd46cdaab1048c3721360e808335d50, tag v6.1.1) instead of the mutable v6.1.1 tag. A SHA is immutable, so a compromised maintainer account cannot repoint it to malicious code in our CI. Add .github/dependabot.yml for the github-actions ecosystem so pinned actions still receive update PRs (keeping the # vX.Y.Z comment in sync) despite no longer floating on a tag.
Adds a maven update entry so Dependabot opens PRs for vulnerable/outdated Java dependencies (e.g. the gson CVE-2022-25647 handled manually in a separate PR), not just GitHub Actions.
Gabrielpanga
force-pushed
the
chore/pin-pr-title-action
branch
from
6e79a9b to
3181ee1
Compare
Gabrielpanga
commented
Jun 10, 2026
Member
Author
There was a problem hiding this comment.
Review — ✅ Approve
Diff: +12 −1, 2 files. Correct and well-scoped.
- SHA pin verified:
48f256284bd46cdaab1048c3721360e808335d50is the actual commit behind tagv6.1.1(resolved via the GitHub refs API). Pinning to a full 40-char SHA is the OpenSSF Scorecard / GitHub-recommended hardening against a mutable tag being repointed by a compromised maintainer account. # v6.1.1comment retained so Dependabot recognizes the pin and keeps it in sync on future bumps.dependabot.ymlwell-formed: now tracks bothgithub-actionsandmavenecosystems (directory: "/", weekly), so vulnerable Java deps (cf. the gson CVE in the sibling PR) get update PRs automatically too.
Note: the earlier test failure was unrelated to this diff (a test-setup issue already fixed on master). This branch has been rebased onto current master, so CI should now be green.
Gabrielpanga
force-pushed
the
chore/pin-pr-title-action
branch
from
3181ee1 to
38aad64
Compare
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
1 participant
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.
What
Hardens the PR-title validation workflow added in #77:
amannn/action-semantic-pull-requestto its full commit SHA (48f256284bd46cdaab1048c3721360e808335d50, tagv6.1.1) instead of the mutablev6.1.1tag. A SHA is immutable, so a compromised maintainer account cannot repoint the tag to malicious code in our CI..github/dependabot.ymlfor thegithub-actionsecosystem (weekly) so pinned actions still receive update PRs, keeping the# vX.Y.Zcomment in sync despite no longer floating on a tag.Why
Pinning to a SHA is the GitHub / OpenSSF Scorecard recommended practice against supply-chain attacks on third-party actions (cf. the
tj-actions/changed-filesincident). Dependabot offsets the only downside — no longer getting patches automatically.