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

chore: Update Dockerfile to node:18.20.3 #2536

Merged
merged 2 commits into from
May 31, 2024

Conversation

pieterocp
Copy link
Contributor

Follow up from #2515

Summary

Appeases security tooling since the updates to node causes some tools to moan.

Checklist

  • The basics
    • I tested these changes manually in my local or dev environment
      • Ran the build locally, used it in my project and it seems to be working fine.
  • Tests
    • Added or updated
    • N/A
      • As far as I am aware, there's no tests for using the projects container in an end to end fashion?
  • Event Tracking
    • I added event tracking and followed the event tracking guidelines
      • (I cannot find any documentation for this so I guess N/A?)
    • N/A
  • Error Reporting
    • [Z] N/A

Additional context

Add any other context about the pull request here. Remove this section if there is no additional context.

@pieterocp pieterocp requested a review from a team as a code owner May 28, 2024 19:13
@pieterocp pieterocp requested review from daniel-white and removed request for a team May 28, 2024 19:13
Dockerfile Outdated Show resolved Hide resolved
Dockerfile Outdated Show resolved Hide resolved
Dockerfile Outdated Show resolved Hide resolved
Changing to use node:18 so that it continues to pull the latest vs a specific version
@brendarearden brendarearden merged commit bce185e into stoplightio:master May 31, 2024
7 checks passed
ilanashapiro pushed a commit to ilanashapiro/prism that referenced this pull request Aug 22, 2024
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