chore(deps): bump sirv from 1.0.0 to 1.0.12

[dependabot-preview]

Bumps sirv from 1.0.0 to 1.0.12.

Release notes

Sourced from sirv's releases.

v1.0.12

Patches

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

Chores

• Adjust GitHub Action env setup (#109): f2ae0f5
• Update Github Action image(s) and Node versions: 9334dfc, cf2de81, c7e0a20
• Add test for filename with space (#102): ede9189 Thank you @​samccone!

v1.0.11

Patches

• (sirv) Add Vary header when gzip or brotli is in use (#95): 86e6733 Thank you @​istarkov~!

v1.0.10

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.

v1.0.9

Patches

• (sirv) More specific ignore regex default (#88): 5e3d7a8 Thank you @​adam-lynch~!

• (sirv) Replace VoidFunction usage in TypeScript definitions (#89): 478b487

v1.0.8

Patches

• (sirv-cli): Add hidden --no-logs option (#85): 714c058
  Does not render "LOGS" output on requests. Unlike --quiet, --no-logs keeps intro banner.

v1.0.7

Patches

• (sirv): Use a separate FILES cache per sirv instance (#84): c69bbfb Thank you @​Rich-Harris~!

• (sirv): Append must-revalidate Cache-Control directive when maxAge: 0 is used: fb31a46 Only appends when immutable option is not in use!

v1.0.6

Patches

... (truncated)

Commits

• 0c832aa v1.0.12
• f2ae0f5 fix(action): adjust Action env setup (#109)
• 9334dfc chore(action): update action images
• cf2de81 chore(action): include Node 14.x
• c7e0a20 chore(action): remove "cache" step
• 8ebca7c fix(sirv-cli): ensure boolean args parsed as such;
• 7c5162a chore(sirv): bump @polka/url version
• ede9189 chore(sirv): add test for filename with space (#102)
• da98454 v1.0.11
• 86e6733 fix: add Vary header when of gzip/brotli in use (#95)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)