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

update node16 to node20 in pr-labels action #6

Merged
merged 5 commits into from
May 2, 2024

Conversation

adamancini
Copy link
Member

@adamancini adamancini commented May 2, 2024

  • update pr-labels action to use node20

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: replicatedhq/required-workflows/.github/actions/pr-labels@main. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Starting with ESLint v9.0.0, the flat config file format will be the default configuration file format. Once ESLint v9.0.0 is released, you can start using the flat config file format without any additional configuration.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: replicatedhq/required-workflows/.github/actions/pr-labels@main. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
@adamancini adamancini changed the title Update action.yml update node16 to node20 in pr-labels action May 2, 2024
list the expected primary label - I was getting confused making a docs PR because type::documentation is not in the PRIMARY_LABELS list.
sgalsaleh
sgalsaleh previously approved these changes May 2, 2024
@adamancini adamancini requested a review from sgalsaleh May 2, 2024 14:58
@adamancini adamancini merged commit e1b609d into main May 2, 2024
3 checks passed
@adamancini adamancini deleted the adamancini-patch-node-20 branch May 2, 2024 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants