dependabot[bot] opened a new pull request, #131: URL: https://github.com/apache/netbeans-antora-ui/pull/131
Bumps the all-dependencies group with 2 updates: [@asciidoctor/core](https://github.com/asciidoctor/asciidoctor.js) and [js-yaml](https://github.com/nodeca/js-yaml). Updates `@asciidoctor/core` from 4.0.0 to 4.0.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/asciidoctor/asciidoctor.js/releases";>@asciidoctor/core's releases</a>.</em></p> <blockquote> <h2>v4.0.1</h2> <h2>Summary</h2> <h2>Release meta</h2> <p>Released on: 2026-07-01 Released by: github-actions[bot] Published by: GitHub</p> <p>Logs: <a href="https://github.com/asciidoctor/asciidoctor.js/compare/...v4.0.1";>full diff</a></p> <h2>Changelog</h2> <h3>Bug Fixes</h3> <ul> <li>Fix reassigned document-body attributes all resolving to their final value — a custom attribute redefined in the body (e.g. <code>:reassigned: one</code> … <code>:reassigned: two</code>) must resolve to the value in scope at each reference (Ruby renders <code>one</code> then <code>two</code>), but every reference rendered the last value when any content preceded the entries (including a document header). The parser reset the shared block-attributes object between blocks with <code>Object.keys(...)</code>, which skips the <code>Symbol</code>-keyed <code>ATTR_ENTRIES_KEY</code>, so the array of <code>AttributeEntry</code> objects leaked and accumulated across blocks; each block’s attribute-entry playback then replayed <strong>every</strong> assignment. The reset now uses <code>Reflect.ownKeys(...)</code> so the entries are cleared too</li> <li>Fix reassigned attributes not resolving correctly when referenced from list item or table cell text (e.g. <code>:x: 1</code> … <code>* item {x}</code> … <code>:x: 2</code> … <code>* item {x}</code>) — unlike paragraph content (resolved lazily during conversion with attribute-entry playback), list item and table cell text is pre-computed eagerly after <code>restoreAttributes()</code> reverted the document to its header state, so body-level attributes were out of scope and rendered as unresolved (<code>{x}</code>) or with the wrong value. <code>_resolveAllTexts</code> now replays each block’s attribute entries in document order (mirroring <code>AbstractBlock#convert</code>) while pre-computing, then restores the header state. In addition, a block carrying <strong>only</strong> <code>Symbol</code>-keyed attribute entries (an <code>:attr:</code> entry immediately preceding a list or table) now still receives them — the parser’s transfer guard used <code>Object.keys(. ..).length</code> (0 for entry-only attributes) instead of <code>Reflect.ownKeys(...).length</code>, matching Ruby’s <code>attributes.empty?</code> where <code>:attribute_entries</code> is counted</li> <li>Fix loss of the structured <code>source_location</code> on log messages emitted through the reader/preprocessor path (e.g. <code>include file not found</code>, <code>unterminated <type> block</code>, unterminated preprocessor conditionals) — these were logged as a plain string with the cursor baked into the text as a <code>"<path>: line <N>: "</code> prefix, so <code>message.getSourceLocation()</code> returned <code>null</code> (regression from 2.x). The reader now logs an auto-formatting message that keeps the cursor as a structured <code>source_location</code>, so <code>getSourceLocation()</code> (<code>getFile()</code>/<code>getLineNumber()</code>) is populated again and <code>getText()</code> stays clean; the stderr <code>Logger</code> still renders the <code>"<path>: line <N>: "</code> prefix. This restores line-anchored diagnostics for downstream tooling (IDE integrations, linters, CI annotations)</li> <li>Fix <code>allow-uri-read</code> not being recognised when declared with an empty value (e.g. <code>allow-uri-read=</code> or <code>attributes: { 'allow-uri-read': '' }</code>) — include resolution checked the attribute’s truthiness via <code>getAttribute</code>, but ’'<code>is falsy in JavaScript while Asciidoctor treats the mere presence of an attribute as enabled; the include reader (Node and browser modes) now checks presence via</code>hasAttribute<code>, matching Ruby’s </code>attr?` semantics</li> <li>Fix incorrect generated type declarations for <code>async</code> substitutor methods — <code>applySubs</code>, <code>subQuotes</code>, <code>subMacros</code>, <code>subPostReplacements</code>, <code>subSource</code>, <code>subCallouts</code>, <code>highlightSource</code>, <code>restorePassthroughs</code> and <code>parseAttributes</code> are all <code>async</code> but their JSDoc <code>@returns</code> declared the unwrapped type (e.g. <code>string</code>), so the emitted <code>.d.ts</code> advertised <code>string</code> instead of <code>Promise<string></code>; callers following the types could concatenate the returned Promise and produce <code>[object Promise]</code>. The JSDoc now declares <code>Promise<…></code> and the <code>.d.ts</code> was regenerated</li> </ul> <h3>Improvements</h3> <ul> <li>Improve typing of <code>MemoryLogger#getMessages()</code> — it previously returned <code>any[]</code>; the <code>LogMessage</code> wrapper class is now exported and <code>getMessages()</code> is declared to return <code>LogMessage[]</code>, so consumers get typed <code>getSeverity()</code> (<code>string</code>), <code>getText()</code> (<code>string</code>) and <code>getSourceLocation()</code> (<code>Cursor | undefined</code>) accessors. The wrapper’s internal <code>_text</code>/<code>_sourceLocation</code> fields were renamed to public <code>text</code>/<code>sourceLocation</code> properties (consistent with <code>severity</code>), providing dual property/getter access</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/asciidoctor/asciidoctor.js/blob/main/CHANGELOG.adoc";>@asciidoctor/core's changelog</a>.</em></p> <blockquote> <p>== v4.0.1 (2026-07-01)</p> <p>Bug Fixes::</p> <ul> <li>Fix reassigned document-body attributes all resolving to their final value — a custom attribute redefined in the body (e.g. <code>:reassigned: one</code> … <code>:reassigned: two</code>) must resolve to the value in scope at each reference (Ruby renders <code>one</code> then <code>two</code>), but every reference rendered the last value when any content preceded the entries (including a document header). The parser reset the shared block-attributes object between blocks with <code>Object.keys(...)</code>, which skips the <code>Symbol</code>-keyed <code>ATTR_ENTRIES_KEY</code>, so the array of <code>AttributeEntry</code> objects leaked and accumulated across blocks; each block's attribute-entry playback then replayed <em>every</em> assignment. The reset now uses <code>Reflect.ownKeys(...)</code> so the entries are cleared too</li> <li>Fix reassigned attributes not resolving correctly when referenced from list item or table cell text (e.g. <code>:x: 1</code> … <code>* item {x}</code> … <code>:x: 2</code> … <code>* item {x}</code>) — unlike paragraph content (resolved lazily during conversion with attribute-entry playback), list item and table cell text is pre-computed eagerly after <code>restoreAttributes()</code> reverted the document to its header state, so body-level attributes were out of scope and rendered as unresolved (<code>{x}</code>) or with the wrong value. <code>_resolveAllTexts</code> now replays each block's attribute entries in document order (mirroring <code>AbstractBlock#convert</code>) while pre-computing, then restores the header state. In addition, a block carrying <em>only</em> <code>Symbol</code>-keyed attribute entries (an <code>:attr:</code> entry immediately preceding a list or table) now still receives them — the parser's transfer guard used <code>Object.keys(...).length</ code> (0 for entry-only attributes) instead of <code>Reflect.ownKeys(...).length</code>, matching Ruby's <code>attributes.empty?</code> where <code>:attribute_entries</code> is counted</li> <li>Fix loss of the structured <code>source_location</code> on log messages emitted through the reader/preprocessor path (e.g. <code>include file not found</code>, <code>unterminated <type> block</code>, unterminated preprocessor conditionals) — these were logged as a plain string with the cursor baked into the text as a <code>"<path>: line <N>: "</code> prefix, so <code>message.getSourceLocation()</code> returned <code>null</code> (regression from 2.x). The reader now logs an auto-formatting message that keeps the cursor as a structured <code>source_location</code>, so <code>getSourceLocation()</code> (<code>getFile()</code>/<code>getLineNumber()</code>) is populated again and <code>getText()</code> stays clean; the stderr <code>Logger</code> still renders the <code>"<path>: line <N>: "</code> prefix. This restores line-anchored diagnostics for downstream tooling (IDE integrations, linters, CI annotations)</li> <li>Fix <code>allow-uri-read</code> not being recognised when declared with an empty value (e.g. <code>allow-uri-read=</code> or <code>attributes: { 'allow-uri-read': '' }</code>) — include resolution checked the attribute's truthiness via <code>getAttribute</code>, but <code>''</code> is falsy in JavaScript while Asciidoctor treats the mere presence of an attribute as enabled; the include reader (Node and browser modes) now checks presence via <code>hasAttribute</code>, matching Ruby's <code>attr?</code> semantics</li> <li>Fix incorrect generated type declarations for <code>async</code> substitutor methods — <code>applySubs</code>, <code>subQuotes</code>, <code>subMacros</code>, <code>subPostReplacements</code>, <code>subSource</code>, <code>subCallouts</code>, <code>highlightSource</code>, <code>restorePassthroughs</code> and <code>parseAttributes</code> are all <code>async</code> but their JSDoc <code>@returns</code> declared the unwrapped type (e.g. <code>string</code>), so the emitted <code>.d.ts</code> advertised <code>string</code> instead of <code>Promise<string></code>; callers following the types could concatenate the returned Promise and produce <code>[object Promise]</code>. The JSDoc now declares <code>Promise<…></code> and the <code>.d.ts</code> was regenerated</li> </ul> <p>Improvements::</p> <ul> <li>Improve typing of <code>MemoryLogger#getMessages()</code> — it previously returned <code>any[]</code>; the <code>LogMessage</code> wrapper class is now exported and <code>getMessages()</code> is declared to return <code>LogMessage[]</code>, so consumers get typed <code>getSeverity()</code> (<code>string</code>), <code>getText()</code> (<code>string</code>) and <code>getSourceLocation()</code> (<code>Cursor | undefined</code>) accessors. The wrapper's internal <code>_text</code>/<code>_sourceLocation</code> fields were renamed to public <code>text</code>/<code>sourceLocation</code> properties (consistent with <code>severity</code>), providing dual property/getter access</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/f9b513dcb9bc9aa3cbdfa825360132ed2d269115";><code>f9b513d</code></a> 4.0.1</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/b27afb519f80b355ee23177327a94429b90c108a";><code>b27afb5</code></a> fix(attributes): play back attribute entries when resolving list/cell text</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/7e110aa4a8ca16de1cc86a3e533c203e2a67a5a2";><code>7e110aa</code></a> fix(attributes): resolve reassigned body attributes per reference</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/52501e782e8d2da0541da9748c1ebb741b15e526";><code>52501e7</code></a> chore(deps): update dependency semver to v7.8.5</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/8e15426f71899914f63ad90fe3c30b6513e7876a";><code>8e15426</code></a> chore(deps): update node.js to v24.18.0</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/1aff5311114cf3e5aeb7533aba33887a7f65fc82";><code>1aff531</code></a> fix(logging): restore structured source_location on reader/preprocessor messages</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/1fc9718c13fa526c36b14027d900b4e35133c94f";><code>1fc9718</code></a> feat(types): expose LogMessage and type MemoryLogger#getMessages()</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/e2e7b456b32c29c6324e0bc645e490ac0aa66df9";><code>e2e7b45</code></a> fix(include): recognize allow-uri-read declared with an empty value</li> <li><a href="https://github.com/asciidoctor/asciidoctor.js/commit/4ba4df603661384affb00b5563628a72b71e439a";><code>4ba4df6</code></a> fix(types): declare Promise return types for async substitutor methods</li> <li>See full diff in <a href="https://github.com/asciidoctor/asciidoctor.js/compare/v4.0.0...v4.0.1";>compare view</a></li> </ul> </details> <br /> Updates `js-yaml` from 5.2.0 to 5.2.1 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md";>js-yaml's changelog</a>.</em></p> <blockquote> <h2>[5.2.1] - 2026-07-02</h2> <h3>Fixed</h3> <ul> <li>Add <code>Map</code> support to !!omap (should work when <code>realMapTag</code> used)</li> </ul> <h3>Security</h3> <ul> <li>Remove quadratic complexity from !!omap <code>addItem</code>. Regression from v5 (usually not critical, because YAML11_SCHEMA is not default anymore).</li> </ul> <h2>4.3.0, 3.15.0 - 2026-06-27</h2> <h3>Security</h3> <ul> <li>Backported <code>maxTotalMergeKeys</code> option.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/nodeca/js-yaml/commit/ac16b42c46c11c5c7f66062bfc78b168b5f07ecd";><code>ac16b42</code></a> 5.2.1 released</li> <li><a href="https://github.com/nodeca/js-yaml/commit/4a864e55eec5044da67ca95a13f48c73e9ae8c0d";><code>4a864e5</code></a> Deps bump</li> <li><a href="https://github.com/nodeca/js-yaml/commit/39f3211a2f01b3c6982710cf21434ab7060acefe";><code>39f3211</code></a> !!omap: add <code>Map</code> support and remove quadratic complexity</li> <li><a href="https://github.com/nodeca/js-yaml/commit/ff17f1e5bbd1d0dcfb9567ff4526f7206a666f7b";><code>ff17f1e</code></a> Changelog update</li> <li><a href="https://github.com/nodeca/js-yaml/commit/8ed15f1cf6a0f1818ea4c0cd5d3973e87af2158f";><code>8ed15f1</code></a> deps bump</li> <li><a href="https://github.com/nodeca/js-yaml/commit/1a562dc14cac81354643e45936cde968b6da324c";><code>1a562dc</code></a> Fix changelog link</li> <li>See full diff in <a href="https://github.com/nodeca/js-yaml/compare/5.2.0...5.2.1";>compare view</a></li> </ul> </details> <br /> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
