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.

Sign up for GitHub

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

Jump to bottom

Upgrade to Node.js 20.12.2 for NestJS #8947

Merged
merged 2 commits into from
May 6, 2024
Merged

Upgrade to Node.js 20.12.2 for NestJS #8947

merged 2 commits into from
May 6, 2024

Conversation

JHyeok
Copy link
Contributor

@JHyeok JHyeok commented Apr 27, 2024

No description provided.

@JHyeok
Copy link
Contributor Author

JHyeok commented Apr 27, 2024 •
edited
Loading

A test failure in PR could be due to the following reasons.
GitHub Actions seems to have encountered a problem with your MongoDB installation.
Error techempower/mongodb:latest: Database was not ready after startup.
Tests based on MySQL and PostgreSQL all passed.

--------------------------------------------------------------------------------
Running Test: nestjs-fastify-mongo
--------------------------------------------------------------------------------
techempower/mongodb:latest: Database was not ready after startup

--------------------------------------------------------------------------------
Running Test: nestjs-mongo
--------------------------------------------------------------------------------
techempower/mongodb:latest: Database was not ready after startup
nestjs-mongo: Step 1/9 : FROM node:20.12.2-slim

@JHyeok JHyeok changed the title Upgrade to Node.js 20.12.2 for NestJS @JHyeok Upgrade to Node.js 20.12.2 for NestJS Apr 27, 2024
@NateBrady23 NateBrady23 merged commit a473c9a into TechEmpower:master May 6, 2024
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@JHyeok @NateBrady23