Bump sirv from 0.4.2 to 1.0.6

[dependabot-preview]

Bumps sirv from 0.4.2 to 1.0.6.

Release notes

Sourced from sirv's releases.

v1.0.6

Patches

• (sirv) Ensure options.setHeaders changes are respected (#79): 25eb012

v1.0.5

Patches

• (sirv) Ensure cached response headers (in "prod" mode) are not mutated between requests (#75, #55): b33bb15 Thank you @imtiazmangerah!

v1.0.4

Patches

• (sirv-cli): Allow graceful HTTP/1 support when --http2 enabled (#74): 4b419bf Does not affect HTTP/2 clients. Instead, allows HTTP/1.1 clients to connect over HTTPS. Thank you @ArtskydJ~!

v1.0.3

Patches

• (sirv-cli) Add --no-clear option to disable console scroll reset (#58): 32a6a2c Default behavior is completely unchanged.

v1.0.2

Patches

• (sirv-cli) Print --host hint when not in use (#70, #71): ec5febc Thank you @mhkeller~! A lot of users are/were unaware that sirv-cli was capable of setting up a network endpoint for your server. The option always existed in the help text's list of options, but it can be easy for things to hide in plain sight! So now the CLI will always show a "Network:" field (to show that it's at least possible) and either the server address if there is one or a short clue about the --host flag.

Chores

• (docs) Add mention of mkcert for alternative SSL certificate generation (#68): 9eea208 Thank you @longrunningprocess~!

v1.0.1

Patches

• (sirv) Set "br" for content-encoding header value (#65): fa4f7db, 7205446 Thank you @DaGhostman~!

Chores

• (sirv) Add additional dotfiles tests: d01fe72
• Update badges: 8785b42

v1.0.0

Breaking

Commits

• fab9f18 v1.0.6
• 25eb012 fix(sirv): respect existing headers;
• e8d8922 chore: bump uvu version
• 45e2daf v1.0.5
• b33bb15 fix(sirv): ensure cached headers are not mutated (#75)
• f8ea6a8 v1.0.4
• 4b419bf fix(sirv-cli): add graceful HTTP/1 compatibility (#74)
• e7ef3f4 v1.0.3
• 32a6a2c feat(cli): add hidden --no-clear option;
• e14ee4e v1.0.2
• 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)