chore(deps): Bump asciidoctor from 4.0.11 to 4.1.0 in the npm-minor-patch group

[dependabot]

Bumps the npm-minor-patch group with 1 update: asciidoctor.

Updates asciidoctor from 4.0.11 to 4.1.0

Release notes

Sourced from asciidoctor's releases.

v4.1.0

Summary

Release meta

Released on: 2026-09-22 Released by: github-actions[bot] Published by: GitHub

Logs: full diff

Changelog

Bug Fixes

• Fix concurrent load()/convert() calls occasionally reporting include file not found (rendering Unresolved directive) -- or image to embed not found or not readable for a data-uri image -- for a file that does exist on disk. The lazy node:fs initializer, duplicated in reader.js and abstract_node.js, published its fs/promises handle one microtask ahead of the fs.constants it needs, so a call entering that window read F_OK/R_OK off undefined; the resulting TypeError was swallowed by the caller’s catch and turned into "the file does not exist". Both values are now published together, once both imports have resolved, and concurrent callers share a single initialization -- factored out into src/node_fs.js, so there is one such initializer for the whole package (#1882)
• Fix XmlSanitizeRx stripping only the first tag of a value. The regex was ported from Ruby without the global flag, while every call site passes it to String#replace, which — unlike Ruby’s gsub — replaces a single match without it. A value holding more than one tag kept everything after the first: doctitle({ sanitize: true }) and the partitioned DocumentTitle, the <meta name="author"> tag of the html5 and semantic-html5 backends, and the DocBook xreflabel attribute. Parser.processAuthors was unaffected: it built its own global copy, which now uses the shared regex
• Fix the warning issued when an asset cannot be found or read (e.g. image::does-not-exist.svg[opts=inline]) always reporting the document as <stdin>. The docfile attribute was looked up on the node instead of on the document, and since docfile is only ever set as a document attribute the lookup never resolved (asciidoctor#4873)

Improvements

• Add an experimental semantic-html5 backend (convert(input, { backend: 'semantic-html5' })) that maps every AsciiDoc node to the HTML element that carries its meaning -- <section>, <figure>/<figcaption>, <aside>, <blockquote>, <details>, <nav>, <time>... -- instead of the AsciiDoc.py-compatible wrapper <div>s of the default html5 backend, with ARIA roles, a <header>/<main>/<footer> page skeleton, an optional XML syntax (htmlsyntax=xml) and its own default stylesheet (asciidoctor-semantic.css, with automatic light/dark themes). This backend is experimentalasciidoctor/asciidoctor#242html5 backend. The converter class is exported as SemanticHtml5Converter. See What’s New for examples, and devdocs/semantic-html5-converter.adoc for the element mapping and design choices
• Add an experimental build-time mode to the built-in highlightjs source highlighter: set :highlightjs-mode: build to colorize source blocks at conversion time instead of in the browser. It supports callouts, linenums, highlight= and start=, and embeds the theme stylesheet (:highlightjs-theme:, default github; :highlightjs-stylesheet: link to link the CDN instead). highlight.js is an optional peerDependency, loaded lazily; in the browser, the adapter falls back to client-side highlighting with a warning
• Syntax highlighter adapters may now be asynchronous: the core awaits highlight() and docinfo(), so an adapter can use an async engine such as Shiki. Existing synchronous adapters are unaffected

Infrastructure

• scripts/strip-internal.js now deletes a generated declaration file that is left with no content -- because every declaration it held was @internal, or because TypeScript emitted nothing for it -- instead of publishing an empty .d.ts (first hit by the new src/node_fs.js, whose exports are all internal)
• Fix the type-generation post-processing (scripts/patch-jsdoc.js) losing the JSDoc of exported object literals that TypeScript synthesizes as namespaces: the comment on the declaration itself was never restored (only the per-property ones), and files in types/ subdirectories were never matched back to their src/ source. The published declarations now carry the previously dropped documentation for ContentModel, Extensions, HttpCacheManager, Logging, several rx namespaces and the experimental buildEngine

Changelog

Sourced from asciidoctor's changelog.

== v4.1.0 (2026-09-22)

Bug Fixes::

• Fix concurrent load()/convert() calls occasionally reporting include file not found (rendering Unresolved directive) -- or image to embed not found or not readable for a data-uri image -- for a file that does exist on disk. The lazy node:fs initializer, duplicated in reader.js and abstract_node.js, published its fs/promises handle one microtask ahead of the fs.constants it needs, so a call entering that window read F_OK/R_OK off undefined; the resulting TypeError was swallowed by the caller's catch and turned into "the file does not exist". Both values are now published together, once both imports have resolved, and concurrent callers share a single initialization -- factored out into src/node_fs.js, so there is one such initializer for the whole package (asciidoctor/asciidoctor.js#1882)
• Fix XmlSanitizeRx stripping only the first tag of a value. The regex was ported from Ruby without the global flag, while every call site passes it to String#replace, which — unlike Ruby's gsub — replaces a single match without it. A value holding more than one tag kept everything after the first: doctitle({ sanitize: true }) and the partitioned DocumentTitle, the <meta name="author"> tag of the html5 and semantic-html5 backends, and the DocBook xreflabel attribute. Parser.processAuthors was unaffected: it built its own global copy, which now uses the shared regex
• Fix the warning issued when an asset cannot be found or read (e.g. image::does-not-exist.svg[opts=inline]) always reporting the document as <stdin>. The docfile attribute was looked up on the node instead of on the document, and since docfile is only ever set as a document attribute the lookup never resolved (asciidoctor/asciidoctor#4873)

Improvements::

• Add an experimental semantic-html5 backend (convert(input, { backend: 'semantic-html5' })) that maps every AsciiDoc node to the HTML element that carries its meaning -- <section>, <figure>/<figcaption>, <aside>, <blockquote>, <details>, <nav>, <time>... -- instead of the AsciiDoc.py-compatible wrapper <div>s of the default html5 backend, with ARIA roles, a <header>/<main>/<footer> page skeleton, an optional XML syntax (htmlsyntax=xml) and its own default stylesheet (asciidoctor-semantic.css, with automatic light/dark themes). This backend is experimentalasciidoctor/asciidoctor#242html5 backend. The converter class is exported as SemanticHtml5Converter. See https://docs.asciidoctor.org/asciidoctor.js/latest/whats-new/[What's New] for examples, and devdocs/semantic-html5-converter.adoc for the element mapping and design choices
• Add an experimental build-time mode to the built-in highlightjs source highlighter: set :highlightjs-mode: build to colorize source blocks at conversion time instead of in the browser. It supports callouts, linenums, highlight= and start=, and embeds the theme stylesheet (:highlightjs-theme:, default github; :highlightjs-stylesheet: link to link the CDN instead). highlight.js is an optional peerDependency, loaded lazily; in the browser, the adapter falls back to client-side highlighting with a warning
• Syntax highlighter adapters may now be asynchronous: the core awaits highlight() and docinfo(), so an adapter can use an async engine such as Shiki. Existing synchronous adapters are unaffected

Infrastructure::

• scripts/strip-internal.js now deletes a generated declaration file that is left with no content -- because every declaration it held was @internal, or because TypeScript emitted nothing for it -- instead of publishing an empty .d.ts (first hit by the new src/node_fs.js, whose exports are all internal)
• Fix the type-generation post-processing (scripts/patch-jsdoc.js) losing the JSDoc of exported object literals that TypeScript synthesizes as namespaces: the comment on the declaration itself was never restored (only the per-property ones), and files in types/ subdirectories were never matched back to their src/ source. The published declarations now carry the previously dropped documentation for ContentModel, Extensions, HttpCacheManager, Logging, several rx namespaces and the experimental buildEngine

Commits

• 9c27e43 4.1.0
• 46ec811 docs: show the version in the What's New title
• 186afb7 docs(converter): sync the semantic HTML5 element mapping with the converter
• 25d28fa fix(converter): omit the semantic HTML5 header when it has nothing to show
• 3060e34 fix(converter): drop the doubled space after a numbered listing caption
• c185923 docs: add a What's New page and condense the unreleased changelog
• a053e08 fix(converter): center the callout number in its badge
• bfebc43 feat(converter): draw every callout number as the same badge
• b470682 test(converter): cover callout numbering across several blocks
• ec3531a fix(converter): give the semantic backend's anchors an accessible name
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions