Skip to content

Update dependencies - #85

Draft
ngcpp-dependency-manager[bot] wants to merge 1 commit into
mainfrom
auto/bump-renovate-deps
Draft

Update dependencies#85
ngcpp-dependency-manager[bot] wants to merge 1 commit into
mainfrom
auto/bump-renovate-deps

Conversation

@ngcpp-dependency-manager

@ngcpp-dependency-manager ngcpp-dependency-manager Bot commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Age Confidence
BlankSpruce/gersemi-pre-commit repository minor 0.28.1 → 0.29.1 age confidence
astral-sh/ruff-pre-commit repository patch v0.16.6 → v0.16.8 age confidence
clang-format pre-commit-python patch ==23.1.0 → ==23.1.1 age confidence
fmt bazel_dep minor 12.1.0 → 12.2.0 age confidence
jlumbroso/free-disk-space action major v1.3.1 → v2.0.0 age confidence
keith/pre-commit-buildifier repository major 8.5.1 → 10.0.1 age confidence
mkdocs-git-revision-date-localized-plugin minor ==1.5.4 → ==1.6.0 age confidence
pymdown-extensions major ==11.0.2 → ==12.0.1 age confidence
rules_cc bazel_dep patch 0.2.22 → 0.2.25 age confidence
ubuntu github-runner major 24.04 → 26.04 age confidence

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

Release Notes

BlankSpruce/gersemi-pre-commit (BlankSpruce/gersemi-pre-commit)

v0.29.1

Compare Source

v0.29.0

Compare Source

astral-sh/ruff-pre-commit (astral-sh/ruff-pre-commit)

v0.16.8

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.8

v0.16.7

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.7

ssciwr/clang-format-wheel (clang-format)

v23.1.1

Compare Source

fmtlib/fmt (fmt)

v12.2.0

Compare Source

jlumbroso/free-disk-space (jlumbroso/free-disk-space)

v2.0.0: — three breaking changes, each with its reason

Compare Source

Breaking changes

  1. swap-storage now defaults to false. Closes #​12 — reported and diagnosed by @​zaikunzhang, whose proposed documentation fallback became the new FAQ. Removing swap can kill a job under memory pressure with no error pointing back at the cleanup step; a default should not break something that elementary.
  2. tool-cache is renamed preinstalled-runtimes. The old name still works until v3.0.0 and prints a deprecation warning. (Its default is unchanged: false, as it has been since 2022.) The new name says what actually breaks when you enable it: the runtimes that actions/setup-node, setup-python, setup-go, and setup-ruby rely on.
  3. Specific options now override general ones. dotnet: false exempts .NET from every removal path, including large-packages. Fixes #​33 — reported by @​ashleney; the overlap was first reported by @​gmij in #​6, and @​ax3l explained the overlapping removal paths and a workaround. The policy is explicit, and this release applies it to .NET; future subject options add and test their own exemptions.

Upgrading from v1 to v2

Most workflows need no change.

  • If you set tool-cache:, rename it to preinstalled-runtimes:. The old name still works until v3.0.0 and prints a warning.
  • If you relied on swap being removed by default, add swap-storage: true. It now defaults to false, because removing swap can kill a job under memory pressure with no error pointing back here (#​12).
  • If you set dotnet: false and were surprised that .NET was still removed, that is fixed — a specific option now overrides a general one (#​33).

Also in this release

A README FAQ ("what are the possible side-effects of these settings?"), CONTRIBUTING.md, and a workflow example for running cleanup conditionally (#​22). The reasons behind every design decision live in docs/adr/ — including ADR-0007, the record of this release's default change, written the day it was decided.

v1.3.2: — security fix and the decision records

Compare Source

Fixes the template-injection pattern in input handling (#​51, by @​nbuckwalt).

Also adds docs/adr/ — the reasoning behind this action: why it exists, what it inherited from apache/flink and ShubhamTatvamasi, what it deliberately does not do, and what is still open.

No behaviour changes. The swap-storage default change ships in the next release.

keith/pre-commit-buildifier (keith/pre-commit-buildifier)

v10.0.1

Compare Source

What's Changed

Full Changelog: keith/pre-commit-buildifier@8.5.1.3...10.0.1

timvink/mkdocs-git-revision-date-localized-plugin (mkdocs-git-revision-date-localized-plugin)

v1.6.0

Compare Source

Highlights

Faster builds

Every page asked git which tag pointed at its commit, and asked again for the site-wide revision commit — the same answer, recomputed for each page. Those lookups are now cached.

The bigger your site, the more you save: on a 1000 page site this removes roughly 18 seconds of build time.

custom_format keeps your own words

If your format had any text around the date directives, that text came out scrambled:

custom_format: "Updated on %d %B %Y"
before:   Up23AMt723 on 23 January 2022
now:      Updated on 23 January 2022

Any format that was made up purely of % directives (including the %d. %B %Y default) was unaffected and still renders exactly as before. Unrecognised directives such as %Q are now left alone instead of being quietly reinterpreted as a different date field.

Creation date commit hash and tag now work

page.meta.git_creation_date_localized_hash and page.meta.git_creation_date_localized_tag were documented but always came back empty. If you use them in a theme override to link back to the commit or release that introduced a page, they now contain what you expect.

Shallow clone warnings reach more setups

The warning that tells you your dates will be wrong because CI only fetched part of the history was silently skipped whenever your .git was not in the directory you ran mkdocs from — a repository inside docs/, or a temporary checkout made by plugins such as monorepo. It now fires there too.

Clearer messages when something goes wrong
  • A bad type: now produces a proper MkDocs config error listing the valid values, instead of a bare AssertionError.
  • If reading git history in parallel fails, the error explains what enable_parallel_processing: false actually does, rather than suggesting a fallback it never attempted.
  • Plugin messages now go through MkDocs' own logger, so they are formatted and coloured like every other message in your build output.
Type hints are now visible

The package ships py.typed, so mypy, pyright and ty can see the plugin's annotations.

Upgrading

mkdocs build --strict is now stricter. Warnings from this plugin previously bypassed MkDocs' warning counter, so --strict ignored them. They now count.

In practice this means a build that combines --strict with a shallow clone will start failing where it used to pass — most commonly GitHub Actions, which checks out with fetch-depth: 1 by default. The dates in that build really are wrong, so the right fix is to fetch the full history:

- uses: actions/checkout@v6
  with:
    fetch-depth: 0

If you would rather keep the build passing as-is, set strict: false in the plugin config to downgrade these messages:

plugins:
  - git-revision-date-localized:
      strict: false

Minimum MkDocs version is now 1.4. The plugin already required MkDocs 1.4 APIs to import at all; the metadata said >=1.0, which meant a resolver could install a combination that could never work. Nothing changes for anyone on 1.4 or newer.

facelessuser/pymdown-extensions (pymdown-extensions)

v12.0.1

Compare Source

12.0.1

  • FIX: BetterEm: fix a case with new logic.

v12.0

Compare Source

12.0

  • BREAK: BetterEm: Complete rewrite. There may be some subtle differences between legacy behavior and new
    CommonMark behavior.

    • * and _ emphasis are handled at the same time to provide more natural nesting.
    • More performant.
    • CommonMark compliant.

  • BREAK: Tilde, Caret, Mark: Rewritten and now built upon the latest BetterEm logic.

    • When used with BetterEm, Tilde, Caret, and Mark will be added to the same delimiter processor under the hood and
      will be parsed at the same time as emphasis, allowing for better nesting logic.
    • More performant. Performance issues reported by (@​lexdotdev).
    • Tilde, Caret, Mark: Allow deletion, insertions, and marking mid-word by default. Set smart_delete,
      smart_insert, or smart_mark, respectively, to enable previous behavior, which prevented mid-word deletion.
    • Tilde, Caret: Add new option no_space to control whether the Pandoc style requirement of "no unescaped
      spaces" is enabled for subscript and superscript, respectively. no_space is enabled by default.

  • NEW: Details, Blocks.Details, Blocks.Admonitions: Allow and handle headers specially in titles.

  • NEW: Quotes: Allow and handle headers specially in callout titles.

  • NEW: BracketSpan: New extension that allows for the creation of spans using a Pandoc style bracket notation.

  • NEW: Arithmatex: Remove deprecated inline_mathjax_preview_format, inline_mathjax_format, and
    inline_generic_format. Use arithmatex_inline_format instead.

  • NEW: Arithmatex: Remove deprecated fence_mathjax_preview_format, fence_mathjax_format, and
    fence_generic_format. Use arithmatex_fenced_format instead.

  • NEW: Emoji: Remove undocumented and deprecated "old style" custom emoji index logic.

  • NEW: Slugs: Remove deprecated uslugify, uslugify_encoded, uslugify_cased, uslugify_cased_encoded, gfm,
    and gfm_encoded. Use the documented slugify method with appropriate arguments instead.

bazelbuild/rules_cc (rules_cc)

v0.2.25

Compare Source

Using bzlmod with Bazel 6 or later:

  1. [Bazel 6] Add common --enable_bzlmod to .bazelrc.

  2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_cc", version = "0.2.25")

Using WORKSPACE:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "rules_cc",
    sha256 = "bd7124a844d0403b4b353bcea34d6c8b2ba88dc26881c26c9ee668da89b71846",
    strip_prefix = "rules_cc-0.2.25",
    url = "https://github.com/bazelbuild/rules_cc/releases/download/0.2.25/rules_cc-0.2.25.tar.gz",
)

load("@rules_cc//cc:extensions.bzl", "compatibility_proxy_repo")

compatibility_proxy_repo()

What's Changed

Notable changes

Default toolchain changes

Rules based toolchain changes

Full Changelog: bazelbuild/rules_cc@0.2.22...0.2.25

Configuration

📅 Schedule: (UTC)

  • 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 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 CLI.

@mingxwa
mingxwa marked this pull request as draft September 14, 2026 08:26

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants