chore(deps): Bump pymdown-extensions from 10.21.2 to 11.0#362
chore(deps): Bump pymdown-extensions from 10.21.2 to 11.0#362dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) from 10.21.2 to 11.0. - [Release notes](https://github.com/facelessuser/pymdown-extensions/releases) - [Commits](facelessuser/pymdown-extensions@10.21.2...11.0) --- updated-dependencies: - dependency-name: pymdown-extensions dependency-version: '11.0' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
The dependency update to pymdown-extensions v11.0 is technically correct and meets quality standards according to Codacy. However, this is a major version release that introduces two significant breaking changes: the removal of support for Python 3.9 and a security-focused restriction in the B64 extension regarding relative links. It is critical to verify that the CI/CD pipeline and deployment environments are using Python 3.10 or newer and that any documentation using the B64 extension does not rely on links outside the defined base_path.
About this PR
- Python 3.9 support has been dropped in this version. Ensure all deployment environments and CI/CD pipelines are updated to Python 3.10 or newer to prevent installation and runtime failures.
- The 11.0 release introduces a restriction in the B64 extension where relative links are restricted to the
base_pathby default. This may break image rendering or links in existing documentation if they reference paths outside of that directory.
Test suggestions
- Verify Markdown rendering remains consistent and functional with the new version.
- Validate B64 extension behavior with relative links to ensure compatibility with new base_path restrictions.
- Confirm the build/runtime environment uses Python 3.10+ since Python 3.9 support is dropped.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify Markdown rendering remains consistent and functional with the new version.
2. Validate B64 extension behavior with relative links to ensure compatibility with new base_path restrictions.
3. Confirm the build/runtime environment uses Python 3.10+ since Python 3.9 support is dropped.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
Bumps pymdown-extensions from 10.21.2 to 11.0.
Release notes
Sourced from pymdown-extensions's releases.
Commits
6d0097bUpdate changelogf4808eaBump version and update changeloga290074Update JS doc depsedce355Merge commit from fork9fb9643Update Python type deps299a129Docs: Update JS deps367d965Drop Python 3.9 (#2902)19ec936Fix issue with empty titles and Tabbed (#2901)4868783Fix npm option18a21f5zensical config should be stored in sdistDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)