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 nock from 13.1.1 to 13.1.4 #161

Closed
wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade nock from 13.1.1 to 13.1.4.

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 3 versions ahead of your current version.
  • The recommended version was released a month ago, on 2021-10-19.
Release notes
Package name: nock from nock GitHub release notes
Commit messages
Package name: nock
  • 8fcc607 fix: send Buffer with length (#2232)
  • 83131b7 style: prettier
  • d8fb723 build(continuous-integration.yaml): set node-version to 16
  • 237272c build(continuous-delivery.yaml): set node-version to 16
  • 39c0089 chore(deps-dev): bump chai from 4.3.3 to 4.3.4 (#2190)
  • c197bbf docs: add async/await example for nock back (#2225)
  • ac8e33d fix(interceptor): don't hang, don't leak resources (#2224)
  • 74e30de fix(types): add missing argument to optionally() (#2223)
  • 7cab6b5 Test reply function returning array with body object (#2219)
  • d3652a5 docs: add laurence-myers as a contributor for code (#2216)

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 snyk-bot requested a review from a team as a code owner November 25, 2021 00:55
@stale
Copy link

stale bot commented Mar 3, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale The issue has not had any recent activity. label Mar 3, 2022
@stale stale bot closed this Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The issue has not had any recent activity.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant