Skip to content

Conversation

@kaitj
Copy link
Collaborator

@kaitj kaitj commented May 4, 2023

Proposed changes

Updates versions of relevant actions to upgrade node12 -> node16

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionalitiy)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

  • Changes have been tested to ensure that fix is effective or that a feature works.
  • Changes pass the unit tests
  • Code has been run through the poe quality task
  • I have included necessary documentation or comments (as necessary)
  • Any dependent changes have been merged and published

Notes

All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

@kaitj kaitj added the maintenance Updates or improvements that do not change functionality of the code label May 4, 2023
@kaitj kaitj merged commit 256bba7 into main May 4, 2023
@kaitj kaitj deleted the node16 branch May 4, 2023 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Updates or improvements that do not change functionality of the code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants