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

[Snyk] Upgrade piscina from 3.2.0 to 4.0.0 #39

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ovhemert
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade piscina from 3.2.0 to 4.0.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 2 days ago, on 2023-06-14.
Release notes
Package name: piscina from piscina GitHub release notes
Commit messages
Package name: piscina
  • 1069a3d 4.0.0
  • 4c126f1 chore: Update CI (#349)
  • b207c31 doc: update release notes
  • d5ccc40 doc: update Node.js recommendation to v16+ (#351)
  • d2051fb test: fix issue at new Node versions (#350)
  • bcae345 Update README.md
  • bb37c26 lint
  • 52be44d Add communication from worker to main thread
  • b9551af feat: expose maxThreads and minThreads out of Piscina instance
  • 622a27f Add Node.js 17.x to the CI matrix
  • 4075d47 Add dependabot

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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