Bump @asciidoctor/core from 2.2.6 to 4.0.11

[dependabot]

Bumps @asciidoctor/core from 2.2.6 to 4.0.11.

Release notes

Sourced from @​asciidoctor/core's releases.

v4.0.11

Summary

Release meta

Released on: 2026-08-18 Released by: ggrossetie Published by: GitHub

Logs: full diff

Changelog

Improvements

• Add Options#getProgramName(), #getUsageLine(), and #getHelpDescription() to the extensible CLI (@asciidoctor/core’s cli.js), letting an extended CLI override just the program name shown by --help-- or the usage line/description individually -- the same wayInvoker#version()can already be overridden;#getHelpPreamble()` remains available to override the whole preamble as a last resort

Bug Fixes

• Fix a footnote inside a list item or table cell being numbered (and listed in the footnotes block) ahead of an earlier footnote in a preceding paragraph, instead of in document order. List item and table cell text is substituted eagerly, ahead of normal body conversion, so any footnote there previously consumed the next footnote number immediately regardless of its actual position in the document; it’s now assigned a placeholder that resolves to the real, document-order number once real conversion reaches that block. Reading a list item’s or table cell’s text/getText() before conversion (e.g. from an extension) no longer fixes the wrong number either -- an unresolved footnote there now previews as 1 rather than consuming the real counter (#1871)

v4.0.10

Summary

Release meta

Released on: 2026-08-17 Released by: ggrossetie Published by: GitHub

Logs: full diff

Changelog

Bug Fixes

• Fix the inline pass:[...] macro escaping its content instead of passing it through unmodified when no explicit substitution list is given, e.g. pass:[<u>underlined</u>] rendered as <u&gt;underlined</u&gt; instead of <u>underlined</u>. The passthrough’s subs was left undefined, which fell through to applySubs()’s NORMAL_SUBS` default parameter instead of the intended "no substitutions" behavior (#1870)
• Fix a footnote inside a list item or table cell not advancing the footnote counter, causing a subsequent footnote elsewhere in the document to reuse the same number and id (invalid HTML, and the later footnote reference would link to the earlier definition). List item and table cell text is substituted eagerly, ahead of normal body conversion, and the footnote counter was unconditionally reset afterwards; it now carries forward into conversion so later footnotes continue numbering from where these left off (#1871)

v4.0.9

Summary

Release meta

Released on: 2026-08-16 Released by: ggrossetie Published by: GitHub

... (truncated)

Changelog

Sourced from @​asciidoctor/core's changelog.

== v4.0.11 (2026-08-18)

Improvements::

• Add Options#getProgramName(), #getUsageLine(), and #getHelpDescription() to the extensible CLI (@asciidoctor/core's cli.js), letting an extended CLI override just the program name shown by --help -- or the usage line/description individually -- the same way Invoker#version() can already be overridden; #getHelpPreamble() remains available to override the whole preamble as a last resort

Bug Fixes::

• Fix a footnote inside a list item or table cell being numbered (and listed in the footnotes block) ahead of an earlier footnote in a preceding paragraph, instead of in document order. List item and table cell text is substituted eagerly, ahead of normal body conversion, so any footnote there previously consumed the next footnote number immediately regardless of its actual position in the document; it's now assigned a placeholder that resolves to the real, document-order number once real conversion reaches that block. Reading a list item's or table cell's text/getText() before conversion (e.g. from an extension) no longer fixes the wrong number either -- an unresolved footnote there now previews as 1 rather than consuming the real counter (asciidoctor/asciidoctor.js#1871)

== v4.0.10 (2026-08-17)

Bug Fixes::

• Fix the inline pass:[...] macro escaping its content instead of passing it through unmodified when no explicit substitution list is given, e.g. pass:[<u>underlined</u>] rendered as <u>underlined</u> instead of <u>underlined</u>. The passthrough's subs was left undefined, which fell through to applySubs()'s NORMAL_SUBS default parameter instead of the intended "no substitutions" behavior (asciidoctor/asciidoctor.js#1870)
• Fix a footnote inside a list item or table cell not advancing the footnote counter, causing a subsequent footnote elsewhere in the document to reuse the same number and id (invalid HTML, and the later footnote reference would link to the earlier definition). List item and table cell text is substituted eagerly, ahead of normal body conversion, and the footnote counter was unconditionally reset afterwards; it now carries forward into conversion so later footnotes continue numbering from where these left off (asciidoctor/asciidoctor.js#1871)

== v4.0.9 (2026-08-16)

Bug Fixes::

• Fix the extension DSL this types (BlockProcessorDslInterface, BlockMacroProcessorDslInterface, InlineMacroProcessorDslInterface, and the document-processor DSLs for preprocessors, tree processors, postprocessors, include processors, and docinfo processors) missing the node-builder helpers -- createSection, createBlock, createList, createListItem, createImageBlock, createInline, parseContent, parseAttributes, and the createBlock/createInline shorthands (createParagraph, createOpenBlock, createExampleBlock, createPassBlock, createListingBlock, createLiteralBlock, createAnchor, createInlinePass) -- even though all of them are available at runtime on the bound processor instance, since every processor type shares the same Processor base class (matching Ruby's Asciidoctor::Extensions::Processor)
• Fix JSDoc Document type references across abstract_node.js, extensions.js, parser.js, syntax_highlighter.js, and table.js (and the corresponding generated .d.ts files) resolving to the ambient DOM Document type instead of Asciidoctor's own Document class from document.js. None of those source files imported Document, so TypeScript resolved the unqualified name to lib.dom.d.ts — getDocument(), extension processor callbacks (Preprocessor#process(), TreeProcessor#process(), etc.), Parser methods, SyntaxHighlighterBase methods, and Table.Cell#getInnerDocument() were all typed against the browser DOM document rather than the Asciidoctor document, silently defeating type checking on any code calling Asciidoctor Document methods on the result
• Fix logging.js logging a spurious CORS error to the console in some browsers (e.g. Firefox) on first use. The per-execution logger context lazily probes for node:async_hooks and falls back to null when unavailable, but the dynamic import('node:async_hooks') itself was still attempted in the browser, where it is treated as a cross-origin fetch and rejected -- caught safely, but still logged by the browser regardless. The import is now skipped entirely when process is undefined (i.e. outside Node.js)

Infrastructure::

• Add compile-only type tests (test/types/document_type.test-d.ts) guarding against the Document DOM-leak regression above, covering AbstractNode#getDocument(), Preprocessor/TreeProcessor/Postprocessor/IncludeProcessor/DocinfoProcessor's process()/handles(), Registry#activate(), and SyntaxHighlighterBase's docinfo()/writeStylesheet()/writeStylesheetToDisk()

== v4.0.8 (2026-08-06)

Improvements::

• Export Severity ({ DEBUG, INFO, WARN, ERROR, FATAL, UNKNOWN }) from @asciidoctor/core's public API (index.js and browser.js). Previously the constant existed only inside logging.js and was not re-exported, so a custom logger built with LoggerManager.newLogger(name, { add }) had no way to compare the (already-numeric) severity argument against named levels without redeclaring the map by hand
• Wire up the pipe constructor option on Logger (new Logger({ pipe })), mirroring Ruby's Logger.new(logdev). It previously had no effect — _writeln() always wrote to process.stderr/console.error regardless of the option. pipe now accepts anything with a write(line) method, or a function called as (line, severity) — the numeric severity lets a function-style pipe route by level (e.g. console.error for ERROR+, console.warn for WARN) without subclassing Logger, overriding add(), or touching the internal _writeln() method

Infrastructure::

• Add compile-only type tests (test/types/logging.test-d.ts) covering the Logger constructor's pipe option (both the object {write} form and the severity-aware (line, severity) function form, plus a negative @ts-expect-error case for an invalid pipe value) and LoggerManager.newLogger()'s add/postConstruct override shape

== v4.0.7 (2026-07-31)

Bug Fixes::

• Fix PathResolver#partitionPath()/#expandPath() dropping a slash from file:/// (and other triple-slash) URIs, turning file:///Users/guillaume/foo.png into file://Users/guillaume/foo.png — a malformed URL whose "host" (Users) browsers reject as Not allowed to load local resource. UriSniffRx only ever matches up to 2 slashes after the scheme, so for a triple-slash URI the 3rd slash is left in the remainder to partition into segments; partitionPath() unconditionally filtered out all empty segments (including that leading one), silently discarding the information needed to reconstruct the slash on joinPath(). It now mirrors Ruby's String#split('/') semantics and drops only trailing empty segments, keeping leading ones intact

== v4.0.6 (2026-07-26)

Bug Fixes::

... (truncated)

Commits

• de8cb78 4.0.11
• bef7cfd feat(cli): allow overriding the program name shown in --help
• e11ad7b refactor(core): auto-detect real conversion instead of a separate _resolvedTe...
• a606c47 fix(core): don't lock in footnote numbering when list/cell text is read befor...
• 3bdab99 fix(core): footnote inside list item or table cell numbered ahead of earlier ...
• af405a0 4.0.10
• 28ccd0c fix(core): footnote inside list item or table cell not advancing counter
• 3b71cf0 fix(core): pass:[] inline macro escapes content instead of passing it through
• 4077572 4.0.9
• 4303dfd fix(core): expose node-builder helpers on every extension DSL, not just Block...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​asciidoctor/core since your current version.