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 sirv from 1.0.10 to 1.0.12 #4

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

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade sirv from 1.0.10 to 1.0.12.

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 3 months ago, on 2021-05-24.
Release notes
Package name: sirv
  • 1.0.12 - 2021-05-24

    Patches

    • (sirv-cli): Ensure boolean options are parsed as booleans (#97): 8ebca7c
    • (sirv): Bump @ polka/url dependency version: 7c5162a

    Chores

  • 1.0.11 - 2021-01-30

    Patches

  • 1.0.10 - 2020-12-07

    Patches

    • (sirv) Use Cache-Control: no-cache when both dev & etag are enabled (#90): c8fe11b
      By default dev-mode always used no-store – but this also means that any ETag on the response is ignored too. Changing this to no-cache allows the browser to remember the ETag and send if as the If-None-Match header on next request.
from sirv GitHub release notes
Commit messages
Package name: sirv

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.

1 participant