fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next-sitemap	^3.1.30 -> ^3.1.31
stylelint (source)	^14.14.1 -> ^14.15.0

---

Release Notes

iamvishnusankar/next-sitemap

v3.1.31

Compare Source

Changes:

• 41e25b8 Merge pull request #​523 from iamvishnusankar/dependabot/npm_and_yarn/next-13.0.2
• e83083b Bump next from 12.3.1 to 13.0.2

This list of changes was auto generated.

stylelint/stylelint

v14.15.0

Compare Source

• Added: --globby-options flag (#​6437) (@​sidverma32).
• Added: custom message formatting for at-rule-disallowed-list, declaration-property-unit-disallowed-list, declaration-property-value-disallowed-list, function-disallowed-list, and property-disallowed-list (#​6463) (@​chloerice).
• Added: support autofix with checkAgainstRule (#​6466) (@​aaronccasanova).
• Added: support for reporting with custom severity (#​6444) (@​aaronccasanova).
• Added: support to checkAgainstRule with custom rules (#​6460) (@​aaronccasanova).
• Fixed: tally output of string formatter colorized (#​6443) (@​ybiquitous).
• Fixed: usage of the import-lazy package to fit bundlers (#​6449) (@​phoenisx).

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

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	Nov 13, 2022 at 10:13AM (UTC)

[pull-request-quantifier-deprecated]

This PR has 4 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       : +2 -2
Percentile : 1.6%

Total files changed: 2

Change summary by file extension:
.json : +2 -2
.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 detected.
• 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.

[github-actions]

Lighthouse Report

✨ https://blog-ad183oe18-sabertaz.vercel.app/

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	93
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-ad183oe18-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	95
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-ad183oe18-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-ad183oe18-sabertaz.vercel.app/books

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	100
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-ad183oe18-sabertaz.vercel.app/about

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

[codecov]

Codecov Report

Merging #999 (758b56a) into main (793ccb8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #999   +/-   ##
=======================================
  Coverage   99.42%   99.42%           
=======================================
  Files         176      176           
  Lines        1039     1039           
  Branches       88       88           
=======================================
  Hits         1033     1033           
  Misses          5        5           
  Partials        1        1           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.