fix(deps): update dependency next-sitemap to ^3.1.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next-sitemap	^3.0.5 -> ^3.1.1

---

Release Notes

iamvishnusankar/next-sitemap

v3.1.1

Compare Source

Changes:

• ff1ee4e Merge pull request #​419 from iamvishnusankar/fix-missing-dist-directory
• 0e5dcab Version bump
• a9a86ed Fix: Missing dist/ directory for v3.0.10 [ #​418 ]

This list of changes was auto generated.

v3.0.10

Compare Source

Changes:

• 2b8d581 Merge pull request #​417 from iamvishnusankar/fix-azure-build-erros
• 007667a Fix azure-pipeline
• ee14bc6 Merge pull request #​408 from iamvishnusankar/dependabot/npm_and_yarn/corex/workspace-4.0.16
• 19594f1 Bump @​corex/workspace from 4.0.14 to 4.0.16
• 4cf3d15 Merge pull request #​407 from iamvishnusankar/dependabot/npm_and_yarn/corex/deepmerge-4.0.16
• 1514d58 Bump @​corex/deepmerge from 4.0.14 to 4.0.16
• 8d59048 Merge pull request #​409 from iamvishnusankar/dependabot/npm_and_yarn/types/react-18.0.12
• 47094bc Bump @​types/react from 18.0.10 to 18.0.12
• 6c264ca Merge pull request #​410 from iamvishnusankar/dependabot/npm_and_yarn/turbo-1.2.16
• 2723720 Bump turbo from 1.2.14 to 1.2.16

This list of changes was auto generated.

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
blog	✅ Ready (Inspect)	Visit Preview	Jun 19, 2022 at 4:54PM (UTC)

[github-actions]

Lighthouse Report

🚦 Waiting for the Vercel preview ...

[codecov]

Codecov Report

Merging #926 (2982514) into main (8efb526) will not change coverage.
The diff coverage is n/a.

❗ Current head 2982514 differs from pull request most recent head 8bd2170. Consider uploading reports for the commit 8bd2170 to get more accurate results

@@           Coverage Diff           @@
##             main     #926   +/-   ##
=======================================
  Coverage   99.41%   99.41%           
=======================================
  Files         175      175           
  Lines        1023     1023           
  Branches       84       84           
=======================================
  Hits         1017     1017           
  Misses          5        5           
  Partials        1        1           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8efb526...8bd2170. Read the comment docs.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.