Skip to content

fix: set node version for npm-publish @W-16974485@ #241

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

Merged

Conversation

ravijayaramappa
Copy link
Collaborator

What does this PR do?

What issues does this PR fix or reference?

@ravijayaramappa ravijayaramappa requested a review from a team as a code owner November 4, 2024 19:01
@ravijayaramappa ravijayaramappa force-pushed the ravi/252-patch/set-node-version-for-release branch from 732a160 to 672925d Compare November 4, 2024 19:03
@ravijayaramappa ravijayaramappa merged commit fe90b91 into 252-patch Nov 4, 2024
11 checks passed
@ravijayaramappa ravijayaramappa deleted the ravi/252-patch/set-node-version-for-release branch November 4, 2024 20:13
ravijayaramappa added a commit that referenced this pull request Nov 4, 2024
* fix: set node version for npm-publish @W-16974485@

* fix: setup nodejs to v20 for CI scripts

* fix: set nodeVersion for nuts workflow
ravijayaramappa added a commit that referenced this pull request Nov 6, 2024
* fix: customize CI for node v20 @W-16974485@

* fix: add debug logs to figure out npm tag issue @W-16974485@ (#236)

* fix: set node version for npm-publish @W-16974485@ (#241)

* fix: set node version for npm-publish @W-16974485@

* fix: setup nodejs to v20 for CI scripts

* fix: set nodeVersion for nuts workflow
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.

2 participants