build(deps): bump pymdown-extensions from 10.21.3 to 11.0.1 in /docs

[dependabot]

Bumps pymdown-extensions from 10.21.3 to 11.0.1.

Release notes

Sourced from pymdown-extensions's releases.

11.0.1

• FIX: BetterEm: Fix regex pattern inefficiencies.
• FIX: Tilde: Fix regex pattern inefficiencies.
• FIX: Caret: Fix regex pattern inefficiencies.
• FIX: MagicLink: Fix regex pattern inefficiencies.

11.0

• BREAK: B64: Restricts relative links to base_path by default. Can be disabled by setting new restrict_path option to False. The new root_path can be specified if paths are desired to be restricted to a different location separate base_path which is also used as a relative base for image paths.
• NEW: Drop Python 3.9 support.
• FIX: Tabbed: Fix issue where an empty title would cause an exception.

Commits

• c684985 Merge commit from fork
• 6d0097b Update changelog
• f4808ea Bump version and update changelog
• a290074 Update JS doc deps
• edce355 Merge commit from fork
• 9fb9643 Update Python type deps
• 299a129 Docs: Update JS deps
• 367d965 Drop Python 3.9 (#2902)
• 19ec936 Fix issue with empty titles and Tabbed (#2901)
• 4868783 Fix npm option
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Summary by CodeRabbit

• Documentation
  • Updated the documentation tooling dependency to a newer version.
  • Refreshed package verification details to support the update.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

📝 Walkthrough

Walkthrough

The documentation requirements update pins pymdown-extensions from 10.21.3 to 11.0.1. It also replaces both associated package integrity hashes.

Suggested reviewers: mgencur

🚥 Pre-merge checks | ✅ 11

✅ Passed checks (11 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The HEAD patch changes only docs/requirements.txt, updating pymdown-extensions and two hashes; it adds no Ginkgo tests or test titles.
Test Structure And Quality	✅ Passed	The patch changes only docs/requirements.txt to update pymdown-extensions and hashes; it adds or modifies no Ginkgo tests, so the test-quality check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	The commit changes only docs/requirements.txt, updating a pinned Python dependency and hashes; it adds no manifests, operator code, controllers, or scheduling constraints.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The pull request changes only docs/requirements.txt; it adds no Ginkgo e2e tests, IPv4 assumptions, or external connectivity requirements.
No-Weak-Crypto	✅ Passed	The commit changes only docs/requirements.txt: a pymdown-extensions pin and SHA-256 package hashes. No prohibited algorithm, custom crypto, or secret comparison appears in added lines.
Container-Privileges	✅ Passed	The commit changes only docs/requirements.txt to update pymdown-extensions and hashes; the patch contains no container/Kubernetes privilege settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR changes only docs/requirements.txt: one dependency version and two SHA-256 hashes. It adds no logging code or sensitive data.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the dependency upgrade in the /docs directory.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/pip/docs/pymdown-extensions-11.0.1

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign csrwng for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[coderabbitai]

🧹 Nitpick comments (1)

docs/requirements.txt (1)

301-303: 🔒 Security & Privacy | 🔵 Trivial

Add supply-chain attestations for the documentation artifact.

CI already installs docs/requirements.txt with pip install --require-hashes. The workflow does not generate an SBOM or provenance attestation, or sign the uploaded docs-site artifact with Sigstore/cosign. Add these controls, or document the higher-level pipeline that applies them before deployment.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/requirements.txt` around lines 301 - 303, Add supply-chain controls to
the documentation build workflow that installs docs/requirements.txt: generate
an SBOM and provenance attestation, and sign the uploaded docs-site artifact
with Sigstore or cosign. If these controls are implemented by a higher-level
deployment pipeline instead, document that pipeline and its enforcement point
near the documentation artifact flow.

Source: Path instructions

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/requirements.txt`:
- Around line 301-303: Add supply-chain controls to the documentation build
workflow that installs docs/requirements.txt: generate an SBOM and provenance
attestation, and sign the uploaded docs-site artifact with Sigstore or cosign.
If these controls are implemented by a higher-level deployment pipeline instead,
document that pipeline and its enforcement point near the documentation artifact
flow.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 034f993d-5a2a-49ae-874b-a97980ea8e09

📥 Commits

Reviewing files that changed from the base of the PR and between a26a7a4 and fa508e0.

📒 Files selected for processing (1)

• docs/requirements.txt

[openshift-ci]

rebase

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dependabot]

Looks like pymdown-extensions is no longer a dependency, so this is no longer needed.