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

BREAKING CHANGE: migrate to node test runner and fastify v5 #374

Merged
merged 3 commits into from
Dec 17, 2024

Conversation

ilteoood
Copy link
Contributor

@ilteoood ilteoood commented Dec 16, 2024

  • migrated to node test runner
  • node engine to v20
  • fastify v5

Note: I was not able to test it locally as the credentials on the vault are expired.

Copy link
Contributor

No linked issues found. Please add the corresponding issues in the pull request description.
Use GitHub automation to close the issue when a PR is merged

@ilteoood ilteoood changed the title BREAKING CHANGE: migrate to node test runner BREAKING CHANGE: migrate to node test runner and fastify v5 Dec 16, 2024
})

t.test('sdk error', async (t) => {
test('sdk error', async (t) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to await these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are awaiting the rejection

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean the test. I remember children tests needing awaiting, but I'm not sure if this applies all the time or it depends

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh Sorry. No, because we are using the describe on top.

@simoneb simoneb merged commit a432b35 into nearform:master Dec 17, 2024
1 of 6 checks passed
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