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

Warning about node.js 12 deprecation in github actions #621

Closed
2 tasks done
jphickey opened this issue Nov 23, 2022 · 0 comments · Fixed by #622
Closed
2 tasks done

Warning about node.js 12 deprecation in github actions #621

jphickey opened this issue Nov 23, 2022 · 0 comments · Fixed by #622
Assignees

Comments

@jphickey
Copy link
Contributor

Checklist (Please check before submitting)

  • I reviewed the Contributing Guide.
  • I performed a cursory search to see if the bug report is relevant, not redundant, nor in conflict with other tickets.

Describe the bug
Github produces a warning about node.js 12 being obsolete with every workflow run. It has been fixed upstream, but CFS uses the old version. This can be fixed by updating the version of the action from v2 to v3.

To Reproduce
Run any of the reusable github workflows that use the "v2" actions.

Expected behavior
Should not use deprecated versions of actions

System observed on:
Github hosted runner

Reporter Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this Nov 23, 2022
@jphickey jphickey added CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) and removed CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) labels Nov 30, 2022
jphickey added a commit to jphickey/cFS that referenced this issue Dec 1, 2022
Update from v1 to v2 on this 3rd party action
dzbaker added a commit that referenced this issue Dec 6, 2022
@dzbaker dzbaker closed this as completed in 749b8ef Dec 6, 2022
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 a pull request may close this issue.

1 participant