chore(deps): Bump antora from 3.1.15 to 3.2.0 in the npm-minor-patch group

[dependabot]

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

Updates antora from 3.1.15 to 3.2.0

Changelog

Sourced from antora's changelog.

== 3.2.0 (2026-08-29)

=== Changed

• site-generator: Log original error message when Antora extension is suspected to be Asciidoctor extension
• Upgrade js-yaml to 5.3.x (playbook-builder, content-aggregator, ui-loader)

=== Fixed

• Don't crash if pub property not set on start page

== 3.2.0-rc.3 (2026-08-12)

=== Added

• playbook-builder: Add antoraVersion property to playbook to provide access to Antora core version (#1236)
• content-classifier: Modify ContentCatalog#getComponentVersion to return latest component version if version is unspecified (#1231)
• asciidoc-loader: Pass standalone option through to Asciidoctor#load API (#1228)
• asciidoc-loader: Add antoraResourceRefs option to control whether Antora resource ref integration is enabled; pass through safe, docfile, and docdir options as well (#1241)
• file-publisher: Update publishFiles to accept an array of files as alternative to array of catalogs (#1235)

=== Changed

• logger: Use src.abspath (absolute path) as file path in log message, if available, even if origin is not set
• playbook-builder: Allow collection keys (array or map) in playbook to be null (#1233)
• playbook-builder: Map --stacktrace CLI option to runtime.stacktrace property on playbook (#1227)
• content-classifier: Change createFile method to set module property to ROOT if not set when inflating src
• content-classifier: Change createFile method to compute and assign path property if not set if input is not a Vinyl instance
• asciidoc-loader: Always prefix docname with family segment if family is not page (#1232)
• navigation-builder: Assign pathname property to navigation entry with internal url when url has a hash (i.e., fragment) (#1237)
• file-publisher: Don't output site if output dir is null; still allow destinations to be null (#1234)
• file-publisher: Only allow primary output dir to set path for fs destination if first entry and path key is not set (#1238)
• file-publisher: Honor empty output destinations; require entry for primary fs destination if destinations key is set (#1240)
• cli: Pass --stacktrace argument to buildPlaybook (#1227)

=== Fixed

• playbook-builder: Don't crash when coercing CLI option value if target collection is null; related to #1233
• file-publisher: Honor clean: false set on output destination when default clean value is true

== 3.2.0-rc.2 (2026-06-20)

=== Added

• content-classifier: Add create argument as second argument to addFile method on content catalog for backwards compatibility; default to true

=== Changed

• content-classifier: Convert contents to Buffer if contents is string for file passed to createFile method on content catalog; only used if input file is not a Vinyl object (#1226)

... (truncated)

Commits

• 85665d0 release 3.2.0
• 79f23d7 add Node.js 26 to test matrix
• 04c952a upgrade xmldom
• 4b923ed update declared supported versions of Node.js
• ecc28eb update release date on what's new page
• 03b788c add missing entries from what's new page
• 058f436 apply pending formatting to example code
• 9452cca upgrade js-yaml
• 621fe93 refresh dependency lock file
• 57a244e remove unused images
• 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

[kw-tmueller]

Root cause of the red build: Antora 3.2.0 migrated to js-yaml 5, so @antora/playbook-builder calls yaml.CORE_SCHEMA.withTags(yaml.mergeTag) at module load — neither symbol exists in js-yaml 4, which the overrides block was forcing into it. Those overrides came from #99 as a workaround for 3.1.15's vulnerable ~4.1 pin and are obsolete here: 3.2.0 resolves js-yaml 5.4.1 itself, the version already declared as a direct dependency, so #99's security goal holds with no override at all.

Removing them (78e0a21) leaves a single hoisted js-yaml 5.4.1. Verified locally on this branch: npm ci clean, npm run antora builds 4618 files across 19 component versions, npm test 42 pass / 0 fail, npm run pagefind indexes 485 pages, and npm audit reports no js-yaml advisories. CI build is green.