fix: use v4 tag for setup-node in workflow#14
Merged
Conversation
snehshah22
force-pushed
the
fix/workflow-setup-node
branch
3 times, most recently
from
cffb1de to
036728c
Compare
snehshah22
force-pushed
the
fix/workflow-setup-node
branch
from
036728c to
087867c
Compare
chriskinzel
approved these changes
Apr 8, 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
2 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.
This Pull Request fixes the broken Notebook MCP Bundle Check workflow.
The Problem: The recently merged file .github/workflows/notebook-mcp-check.yml attempted to pin actions/setup-node to a full commit SHA for static security (64745409647f540ba9c1a129988bd580887fb902). However, that specific SHA could not be verified or resolved by GitHub, leading to hard job failures saying "unable to find version".
The Fix: I have fallen back to pointing purely at the stable release branch tag: uses: actions/setup-node@v4
This fixes the resolver failures and will allow the status check barrier to evaluate correctly again.