Skip to content
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

Ensure GitHub Action runs in specified version of node #1006

Merged
merged 4 commits into from
Jun 12, 2024

Conversation

tevanoff
Copy link
Contributor

@tevanoff tevanoff commented Jun 11, 2024

Revert this small bit that was added in #991.

It was not necessary for the change made in that PR, and it caused the Storybook build command to run with the node version specified by the GitHub Action (node 20), instead of the version of node that is installed in the workflow using something like actions/setup-node.

Fixes #1000
Fixes #1002

📦 Published PR as canary version: 11.5.5--canary.1006.9486086143.0

✨ Test out this PR locally via:

npm install chromatic@11.5.5--canary.1006.9486086143.0
# or 
yarn add chromatic@11.5.5--canary.1006.9486086143.0

Copy link

codacy-production bot commented Jun 11, 2024

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00% (target: -1.00%) 100.00% (target: 80.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (a1fb89f) 8458 6677 78.94%
Head commit (710c589) 8460 (+2) 6679 (+2) 78.95% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#1006) 3 3 100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences


🚀 Don’t miss a bit, follow what’s new on Codacy.

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

Welp, turns out that yarn 4 does NOT enforce the node version specified in
engines anymore. So even if we have a version of node set, but yarn is
running in a different version of node, the commands won't fail. Without
that enforcement, this test won't work.

This reverts commit 7539866.
When set to true, this ran the commands with the node version set by
the action (node20), not the version set in the workflow.
@tevanoff tevanoff marked this pull request as ready for review June 12, 2024 00:10
@tevanoff tevanoff added release Auto: Create a `latest` release when merged patch Auto: Increment the patch version when merged labels Jun 12, 2024
Copy link
Contributor

@ethriel3695 ethriel3695 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get the correct Node version run on my end, and Chromatic also succeeds, even though the Node version does not match. I also get a green Chromatic run.
Screenshot 2024-06-11 at 18 30 29
Screenshot 2024-06-11 at 18 31 37

node-src/tasks/build.ts Outdated Show resolved Hide resolved
Co-authored-by: Gert Hengeveld <info@ghengeveld.nl>
@tevanoff tevanoff added this pull request to the merge queue Jun 12, 2024
Merged via the queue into main with commit 022aef3 Jun 12, 2024
22 checks passed
@tevanoff tevanoff deleted the todd/fix-exec-build branch June 12, 2024 16:13
@ghengeveld
Copy link
Member

🚀 PR was released in v11.5.4 🚀

@ghengeveld ghengeveld added the released Verdict: This issue/pull request has been released label Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Auto: Increment the patch version when merged release Auto: Create a `latest` release when merged released Verdict: This issue/pull request has been released
Projects
None yet
3 participants