chore(deps): update dependency vitepress-sidebar to v1.39.0 - #48
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
artemkovalyov
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.36.1→1.39.0Release Notes
jooy2/vitepress-sidebar (vitepress-sidebar)
v1.39.0Compare Source
useTitleFromFileHeadingno longer reads a comment written inside the frontmatter as the heading of a page. A comment starts with#, exactly like anh1does, so a line such as# https://vitepress.dev/reference/default-theme-home-pageleft at the top of a frontmatter became the title of the item. The frontmatter block is now removed before the content is read for a heading, and a file that holds no heading below it falls back to its file name, as it already did. The block is located by its delimiters, the way VitePress locates it, so it is removed even when what it holds is not valid YAML. (#223)sortMenusByFrontmatterOrdernow compares theorderof the frontmatter as a number instead of as text, so a negative or a decimal value is placed where its value belongs.-2no longer comes after-1, and2.25no longer comes after2.5. The sorting relied on thenumericoption ofIntl.Collator, which is a natural sort of the digit runs inside a string and reads neither a leading-as a sign nor a.as a decimal point, so it only agreed with numeric order for small positive integers. Sorting by a file name or a title is unaffected, as it is still the natural sort that is wanted there. Anorderthat does not read as a number now falls back tofrontmatterOrderDefaultValue, as the documentation describes, instead of being sorted asNaN. (#233)v1.38.0Compare Source
sortMenusByCustomFunctionoption, which sorts the items of every folder with a function of your own, written in the formArray.prototype.sortexpects. Each item being compared carriestext,link,fileName,filePath,isDirectory,createDate,modifyDateandfrontmatter, so an order can be decided from something the other options never read, such as a date kept in version control. The file times and the frontmatter are only read when the function accesses them. It decides the order of a whole folder by itself, so it cannot be used together with another sorting option, and a function cannot be written in JSON, so it is not available in asidebar.config.json. (#188)withSidebarnow honors thesrcExcludeof the VitePress configuration, so a page that is excluded from the build no longer has to be excluded a second time to keep it out of the sidebar. Its patterns are resolved fromdocumentRootPath, exactly like VitePress resolves them fromsrcDir, and are applied on top ofexcludeByGlobPatternand the other exclusion options rather than replacing them. Excluding a dynamic route template excludes every page it generates.generateSidebaris not given the VitePress configuration, so it cannot readsrcExclude. (#181)sortMenusOrderNumericallyFromLinknow sorts a folder that has no link by its own path, instead of placing every such folder at one end of the list. Folders and files are ordered together by the number in their names even when the titles come from elsewhere, such as withuseFolderTitleFromIndexFileanduseTitleFromFileHeading. (#183)v1.37.0Compare Source
sidebar.config.jsonfile placed in any folder now configures that folder and everything below it. The options it declares take priority over the options passed towithSidebarorgenerateSidebar, anddocumentRootPathcan be omitted when such a file exists. (#166)$folderkey of asidebar.config.jsondescribes the folder it lives in (order,text,link) instead of its contents, and is not inherited by subfolders. A folder can now be ordered, named and linked without anindex.md, and the position of a folder no longer depends on where itsindex.mdsits inside it. (#197)includeDynamicRoutesoption, which shows a dynamic route as the pages it generates instead of as the template file it is generated from. A parameter may appear in a folder name as well, and both a.paths.tsfile and an asynchronouspaths()function are supported. (#199)dynamicRouteTitleParamoption, which names the route parameter that holds the sidebar title of a generated page. A title written as{{ $params.name }}in the template is resolved as well, and theorderanddateparameters are read bysortMenusByFrontmatterOrderandsortMenusByFrontmatterDate.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.