chore(deps): bump zensical from 0.0.33 to 0.0.38 in /docs

[dependabot]

Bumps zensical from 0.0.33 to 0.0.38.

Release notes

Sourced from zensical's releases.

0.0.38

Summary

This version adds link and footnote validation and strict mode – two of the most frequently requested features. Zensical now checks all internal references at build time and reports issues with precise source locations, so broken links don't make it into your published documentation. Unlike MkDocs, which only validates final rendered links, Zensical also checks for unresolved references, as well as unused and shadowed definitions – covering the full lifecycle of a reference from definition to use.

Validation

Zensical scans every Markdown file in your project and resolves all internal references against each other: inline links, reference-style links, footnotes, link definitions, and anchor targets. Every check is individually configurable and enabled by default.

$ zensical build
...
Warning: page does not exist
   ╭─[ index.md:3:14 ]
   │
 3 │ [id]: non-existent.md
   │       ───────┬───────
   │              ╰───────── page does not exist
───╯

The following checks for links and footnotes are now available:

• unresolved_references
• unresolved_footnotes
• unused_definitions
• unused_footnotes
• shadowed_definitions
• shadowed_footnotes
• invalid_links
• invalid_link_anchors

Strict mode

The new --strict command line flag causes the build to fail when any enabled validation check triggers, turning warnings into errors. This is useful for CI pipelines where you want to enforce link integrity and prevent broken documentation from being published:

$ zensical build --strict
...
Warning: unresolved link reference
   ╭─[ index.md:1:35 ]
   │
 1 │ This is an [unresolved reference][id].
   │                                   ─┬
   │                                    ╰── unresolved link reference
───╯
1 issue found
</tr></table> 

... (truncated)

Commits

• 0e7f1d8 chore: release v0.0.38
• 201c615 feature: add link and footnote validation and --strict mode (#175)
• b3c1d91 refactor: use our markdown subclasses
• ce8cbf8 refactor: simplify function definitions after zrx upgrade
• 55c9d26 chore: release v0.0.37
• 5178689 chore: fix ty warning
• 5fd8871 fix: revert change in search processor (regression)
• 99d53f6 feature: add collectors to extract references for link validation
• 9872092 refactor: subclass Markdown processors to extend functionality
• 72ba122 fix: sanitize nested metadata (#582)
• 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)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud