Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix(action): Use action/setup-node instead of unofficial volta action #256

Merged
merged 3 commits into from
Feb 10, 2025

Conversation

andreiborza
Copy link
Member

@andreiborza andreiborza commented Feb 10, 2025

The action now first checks if node is already installed and if so skips action/setup-node, otherwise we ensure node (and thus npm) are installed before running the action.

Additionally, it also marks the GITHUB_WORKSPACE as a safe directory for git so the runner can correctly cd into the repo root for automatic release name determination and commit blaming.

Closes: #249

@andreiborza andreiborza force-pushed the ab/use-setup-node branch 17 times, most recently from c98164b to 4d90098 Compare February 10, 2025 15:00
Copy link
Member

@chargome chargome left a comment

Choose a reason for hiding this comment

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

lgtm

# setup-node doesn't allow absolute paths, so we can't
# just use `github.action_path` to read this out from the `package.json`
# any changes to the runtime need to be reflected here
node-version: 18.17.0
Copy link
Member

Choose a reason for hiding this comment

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

should we use the latest 18 version?

Copy link
Member Author

Choose a reason for hiding this comment

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

I pinned to what's in the package.json. For now I'll keep it like this but will look into bumping this in another PR.

@andreiborza andreiborza merged commit 7e7cd36 into master Feb 10, 2025
15 checks passed
@andreiborza andreiborza deleted the ab/use-setup-node branch February 10, 2025 16:04
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

v1.10.x started breaking with Could not automatically determine release name
2 participants