chore(deps): upgrade to mkdocs-material@9.7.6#908
Conversation
|
Warning Review limit reached
Next review available in: 49 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (10)
WalkthroughThe pull request upgrades the Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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.
Inline comments:
In `@mkdocs.yml`:
- Around line 379-382: The Material config block under extra is using a
misspelled key, so analytics is not being picked up. Update the key in
mkdocs.yml from the typo to the correct extra.analytics name, keeping the
existing provider and property values unchanged. Use the surrounding extra block
to locate the fix.
In `@theme/partials/nav-item.html`:
- Around line 203-209: The leaf-node branch in nav-item.html opens a <li> in the
else path but never closes it before the endif block, leaving the list markup
unbalanced. Update the nav-item template’s leaf branch so the <li> opened around
the nav_item.url link is properly closed after the <a> in the same branch,
matching the section branch’s structure and preserving the existing
render_content(nav_item) behavior.
In `@theme/partials/tabs.html`:
- Around line 8-9: Remove the leftover hardcoded tab links in tabs.html that
duplicate the migrated navigation entries and bypass site URL handling. Update
the tabs rendering to rely on the existing nav.items-driven navigation used by
the template rather than fixed "Stemcells" and "Releases" anchors, so links
respect config.site_url and use_directory_urls. If those pages are still needed,
move them into the navigation configuration instead of keeping them hardcoded in
the tabs partial.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 496b17ce-2743-4b52-a035-8c28b8a1de97
⛔ Files ignored due to path filters (1)
content/images/logo-full-white.pngis excluded by!**/*.png
📒 Files selected for processing (10)
README.mdci/tasks/build.ymlcontent/index.mdmkdocs.ymltheme/partials/copyright.htmltheme/partials/footer.htmltheme/partials/nav-item.htmltheme/partials/nav.htmltheme/partials/source.htmltheme/partials/tabs.html
- Migrated config - Migrated theme overrides Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
ad38b48 to
a896a9b
Compare
This brings the docs up to date with the latest version of Material for MkDocs (v9.7.6):
Noticeable benefits are mostly niceities:
mkdocs.ymlconfig and templates are now aligned with the Material for MKDocs documentationSee also the accompanying PR: cloudfoundry/bosh-io-web#81