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

fix: Update act Dependency to v0.2.61 for Node 20 Actions Support #79

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

Ga13Ou
Copy link
Contributor

@Ga13Ou Ga13Ou commented Apr 22, 2024

Changes

This pull request updates the act dependency in act-js from v0.2.48 to v0.2.61. This update is crucial as it introduces support for Node 20, enabling act-js to handle workflows that utilize the latest versions of GitHub Actions requiring Node 20.

Why is this change necessary?

The current default version of act used by act-js (v0.2.48) does not support Node 20, leading to failures when users attempt to execute workflows that depend on this Node version. By updating to act v0.2.61, we ensure compatibility with workflows having actions designed for Node 20, improving the tool's usability and reliability.

Related issues

@shubhbapna shubhbapna self-requested a review April 23, 2024 21:16
@shubhbapna shubhbapna changed the title Update act Dependency to v0.2.61 for Node 20 Actions Support fix: Update act Dependency to v0.2.61 for Node 20 Actions Support Apr 23, 2024
@shubhbapna shubhbapna merged commit d05b67f into kiegroup:main Apr 23, 2024
5 checks passed
@@ -26,7 +26,7 @@
"nektos/act"
],
"scripts": {
"postinstall": "node scripts/postinstall.js 0.2.48",
"postinstall": "node scripts/postinstall.js 0.2.61",
Copy link
Contributor

Choose a reason for hiding this comment

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

@Ga13Ou does the postinstall actually affect users? Not only the CI / local development of act-js?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes since the postinstall script automatically runs after the npm install... , it means that for users who don't manually/separately install act and use the ACT_BINARYenv variable to point to their version, they will be automatically using the version specified in the postinstall script

Copy link
Collaborator

Choose a reason for hiding this comment

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

Correct. I had added it to fix #23

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah, I see. We haven't faced this because we have always explicitly used the ACT_BINARY so that we control the exact version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants