Pin dependencies

[renovate]

This PR contains the following updates:

Package	Update	Change
mkdocs (source)	pin	>=1.1 -> ==1.3.0
mkdocstrings (changelog)	pin	>=0.18 -> ==0.19.0
pymdown-extensions	pin	>=9.2 -> ==9.5

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

---

Configuration

📅 Schedule: Branch creation - "on the first day of the month" (UTC), 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.

[hugovk]

Do we want to pin the docs dependencies or are lower versions (where needed) enough?

[codecov-commenter]

Codecov Report

Merging #36 (1c6269b) into main (efcbaf6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #36   +/-   ##
=======================================
  Coverage   99.12%   99.12%           
=======================================
  Files           9        9           
  Lines         686      686           
=======================================
  Hits          680      680           
  Misses          6        6           

Flag	Coverage Δ
macos-latest	96.50% <ø> (ø)
ubuntu-latest	97.37% <ø> (ø)
windows-latest	96.20% <ø> (-0.88%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

---

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 efcbaf6...1c6269b. Read the comment docs.

[carterbox]

This is cool! Did you choose the pinning strictness or it just defaults to exact PATCH on some packages and exact MINOR on others?

[carterbox]

Do we want to pin the docs dependencies or are lower versions (where needed) enough?

The docs dependencies are for rendering on readthedocs, so whatever renders on readthedocs should be good. My point is that I don't think providing people too many options to render the docs is necessary when they can just read the prerendered docs on readthedocs.

[hugovk]

This is cool! Did you choose the pinning strictness or it just defaults to exact PATCH on some packages and exact MINOR on others?

I left it to the defaults, except for GitHub Actions:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:base"],
  "labels": ["changelog: skip", "dependencies"],
  "packageRules": [
    {
      "groupName": "github-actions",
      "matchManagers": ["github-actions"],
      "separateMajorMinor": "false"
    }
  ],
  "schedule": ["on the first day of the month"]
}

Normally it doesn't group PR for major bumps, but because GHA is often pinned to major versions (e.g. @v3) I let it group those.

(Re: https://github.com/python-humanize/humanize/blob/21cb4a030f0ff2f05adf32c55955d844d3ea287e/.github/renovate.json)

The docs dependencies are for rendering on readthedocs, so whatever renders on readthedocs should be good. My point is that I don't think providing people too many options to render the docs is necessary when they can just read the prerendered docs on readthedocs.

Yeah, that sounds reasonable, let's go with this.

(On another repo, I needed to mark the requirements.txt as a group for it to bunch PRs together (hugovk/pypistats#344), let's see what happens and add that if needed.)

Thanks!