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

AAE-29442 moving to node 20.18.1 #10500

Merged
merged 2 commits into from
Dec 18, 2024
Merged

Conversation

VitoAlbano
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation
  • Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)

What is the new behaviour?

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

@VitoAlbano VitoAlbano changed the title AAE-0000 - moving to node 20.18.1 AAE-29442 moving to node 20.18.1 Dec 16, 2024
@VitoAlbano VitoAlbano force-pushed the fix/AAE-29442-moving-to-node-20 branch from 8dc793f to 1268e6b Compare December 16, 2024 16:14
@VitoAlbano VitoAlbano force-pushed the fix/AAE-29442-moving-to-node-20 branch from 1268e6b to 4da74d1 Compare December 16, 2024 19:22
@VitoAlbano VitoAlbano merged commit 872fb16 into develop Dec 18, 2024
18 checks passed
@VitoAlbano VitoAlbano deleted the fix/AAE-29442-moving-to-node-20 branch December 18, 2024 11:14
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.

3 participants