Skip to content

Conversation

mojito317
Copy link
Contributor

PR summary

Officially adds node 22 support

Note: An existing issue is required before opening a PR.

PR Checklist

Please make sure that your PR fulfills the following requirements:

  • The commit message follows the
    Angular Commit Message Guidelines.
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • New tests
  • Build/CI related changes
  • Documentation content changes
  • Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@mojito317 mojito317 requested a review from a team as a code owner October 17, 2024 07:19
@mojito317 mojito317 self-assigned this Oct 17, 2024
@mojito317 mojito317 force-pushed the i973-update-for-node-22 branch 2 times, most recently from 7fcc4a6 to 37f7388 Compare October 17, 2024 07:23
@mojito317 mojito317 force-pushed the i973-update-for-node-22 branch from 37f7388 to 2613029 Compare October 18, 2024 07:28
@mojito317 mojito317 merged commit 379cd0c into main Oct 18, 2024
8 checks passed
@mojito317 mojito317 deleted the i973-update-for-node-22 branch October 18, 2024 08:10
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