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 @dotcom-reliability-kit/middleware-log-errors from 1.4.1 to 1.5.4 #526

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

Conversation

asugar13
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @dotcom-reliability-kit/middleware-log-errors from 1.4.1 to 1.5.4.

ℹ️ 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 5 versions ahead of your current version.

  • The recommended version was released 2 years ago.

Release notes
Package name: @dotcom-reliability-kit/middleware-log-errors
  • 1.5.4 - 2023-04-05
  • 1.5.3 - 2023-04-04
  • 1.5.2 - 2023-03-21
  • 1.5.1 - 2023-03-14
  • 1.5.0 - 2023-03-10
  • 1.4.1 - 2022-12-22
from @dotcom-reliability-kit/middleware-log-errors GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

… to 1.5.4

Snyk has created this PR to upgrade @dotcom-reliability-kit/middleware-log-errors from 1.4.1 to 1.5.4.

See this package in npm:
@dotcom-reliability-kit/middleware-log-errors

See this project in Snyk:
https://app.snyk.io/org/asugar13/project/d976477e-22c7-4d22-82e9-6b3003dda604?utm_source=github&utm_medium=referral&page=upgrade-pr
@next-team next-team temporarily deployed to ft-next-synd-snyk-upgra-znji4a January 13, 2025 02:01 Inactive
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.

3 participants