chore(deps): pin dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@commitlint/cli (source)	devDependencies	pin	^17.0.2 -> 17.0.2
@commitlint/config-angular (source)	devDependencies	pin	^17.0.0 -> 17.0.0
@emotion/react	dependencies	pin	^11.9.3 -> 11.9.3
@emotion/styled	dependencies	pin	^11.9.3 -> 11.9.3
@mantine/dates	dependencies	pin	^4.2.9 -> 4.2.9
@mantine/dropzone (source)	dependencies	pin	^4.2.9 -> 4.2.9
@mantine/form (source)	dependencies	pin	^4.2.9 -> 4.2.9
@mantine/hooks (source)	dependencies	pin	^4.2.9 -> 4.2.9
@mantine/modals (source)	dependencies	pin	^4.2.9 -> 4.2.9
@mantine/notifications (source)	dependencies	pin	^4.2.9 -> 4.2.9
@mantine/prism (source)	dependencies	pin	^4.2.9 -> 4.2.9
@mantine/spotlight (source)	dependencies	pin	^4.2.9 -> 4.2.9
@sentry/react	dependencies	pin	^7.1.1 -> 7.1.1
@sentry/tracing	dependencies	pin	^7.1.1 -> 7.1.1
@tauri-apps/api	dependencies	pin	^1.0.1 -> 1.0.1
@tauri-apps/cli	devDependencies	pin	^1.0.0 -> 1.0.0
date-fns	dependencies	pin	^2.28.0 -> 2.28.0
dayjs (source)	dependencies	pin	^1.11.3 -> 1.11.3
detect-browser-language	dependencies	pin	^0.0.2 -> 0.0.2
formik (source)	dependencies	pin	^2.2.9 -> 2.2.9
husky (source)	devDependencies	pin	^7.0.0 -> 7.0.4
i18next (source)	dependencies	pin	^21.8.10 -> 21.8.10
i18next-browser-languagedetector	dependencies	pin	^6.1.4 -> 6.1.4
react-i18next	dependencies	pin	^11.17.2 -> 11.17.2
react-icons	dependencies	pin	^4.4.0 -> 4.4.0
react-slick (source)	dependencies	pin	^0.29.0 -> 0.29.0
react-undraw-illustrations	dependencies	pin	^2.0.3 -> 2.0.3
react-use	dependencies	pin	^17.4.0 -> 17.4.0
stylis	dependencies	pin	^4.1.1 -> 4.1.1
stylis-plugin-rtl	dependencies	pin	^2.1.1 -> 2.1.1
tabler-icons-react (source)	dependencies	pin	^1.49.0 -> 1.49.0

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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.

[netlify]

✅ Deploy Preview for redwoodblog-dev ready!

Name	Link
🔨 Latest commit	cd5e84b
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodblog-dev/deploys/62acefaa43534a00080f5524
😎 Deploy Preview	https://deploy-preview-2--redwoodblog-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Small
Size       : +33 -33
Percentile : 26.4%

Total files changed: 3

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