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 tap from 11.1.3 to 11.1.5 #41

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade tap from 11.1.3 to 11.1.5.

merge advice
ℹ️ 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.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 4 years ago, on 2018-05-09.
Release notes
Package name: tap from tap GitHub release notes
Commit messages
Package name: tap
  • a62dfcf 11.1.5
  • d930902 upgrade deps to avoid security warnings
  • fae29d0 make tests pass in node v10
  • f9d64f6 don't include internal filenames in snapshots
  • 5303417 avoid custom inspect deprecation warning
  • e374e7c add dotenv to the tap 100 list
  • 8635bfb 11.1.4
  • 3346fc1 Don't require argv file list if specified in taprc

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

snyk-bot and others added 7 commits February 23, 2022 05:27
…c0e6aac9aa

[Snyk] Security upgrade node from 14-slim to current-slim
…6bc8352ddb

[Snyk] Fix for 3 vulnerabilities
…911a7f4f16

[Snyk] Security upgrade node from 14-slim to gallium-buster-slim
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