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

support for node-20 #45

Closed
wants to merge 2 commits into from
Closed

support for node-20 #45

wants to merge 2 commits into from

Conversation

v1v
Copy link

@v1v v1v commented Feb 21, 2024

Closes #43

This is a breaking change, see hashicorp/vault-action#526

@tonit
Copy link

tonit commented Feb 28, 2024

would love to have this merged

@saurabh-gadariya
Copy link

Can you please merge this ASAP
node 16 warning is so stressful!

@JakeTowers JakeTowers force-pushed the feature/node-20 branch 2 times, most recently from be4b7f2 to c46ec5b Compare March 25, 2024 09:40
@JakeTowers
Copy link
Collaborator

@IanMoroney not sure why the build is failing on this, I opened a new branch with the exact same changes and the build succeeds...

I thought it was to do with GitHub permissions needed as it seems to fail here - https://github.com/phoenix-actions/test-reporting/blob/main/src/main.ts#L186-L195 and that says it needs the checks: write permissions, but I've had no luck

@IanMoroney
Copy link
Contributor

there is a permission now required @JakeTowers in the ci workflow.

permission:
  checks: write

@IanMoroney
Copy link
Contributor

committed the required change to main

@IanMoroney
Copy link
Contributor

Tested successfully in #47 . Merged to main, so will close the PR in favour of that one with successful CI builds

@IanMoroney IanMoroney closed this Mar 25, 2024
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.

Deprecation warning due to Node 16
5 participants