Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ShaneK
approved these changes
Aug 11, 2026
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
3 participants
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.
Issue URL: N/A
What is the current behavior?
The workflow references its GitHub Actions by floating major tags,
actions/checkout@v4andactions/setup-node@v4. A tag is mutable, so whoever controls the action repository can repoint it at different code, and every subsequent CI run picks that code up with no change on our side. This is the supply chain risk behind the recent run of compromised action releases.Renovate is also scoped to the stackblitz sample apps only, via
includePaths, so nothing under.github/workflowsis visible to it.What is the new behavior?
Both actions are pinned to a full commit SHA, with the version in a trailing comment for readability. A SHA is immutable, so CI runs the exact code that was reviewed. The SHAs and the comment format match what
ionic-frameworkalready uses, keeping the two repos consistent:actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0.github/workflows/**is added toincludePathsinrenovate.json. This is required rather than optional: a pin that is never bumped stops receiving security patches, which would leave us worse off than the floating tags.Does this introduce a breaking change?
Other information
N/A