janhoy commented on PR #5166: URL: https://github.com/apache/solr/pull/5166#issuecomment-6863705311
🤖 Merged current `main` (clean, no conflicts) and bumped the pin to Antora **3.2.2** — the current latest (2026-10-30); 3.2.1 → 3.2.2 is logger fixes only. `engines.node >= 20`, we pin Node 22.18.0. **Now validated** - `buildLocalAntoraSite` + `checkSiteLinks` from a git worktree: pass. Antora reports `worktree: …` against the main `.git`, which is the point of the upgrade. 859 files parsed, 0 link errors; search index (6.9 MB) and search UI present. - The same two tasks from a normal (non-worktree) clone: pass, with identical warnings and link-checker stats. - **`buildOfficialSite`: passes.** 14 Solr component versions (`9_0`–`9_11`, `10_0`, `latest`=10_1) plus 7 Operator versions; 8559 files, 3421 pages, all three sitemaps produced. The nightly config (`-Prefguide.official.includePrereleaseVersions=true`) passes too: 17 Solr versions including `11_0` from `main`, and 8 Operator versions. - **Playbook/attribute parsing: no issue.** The 3.2.0-alpha.9 change (#1115) is in playbook-builder and applies to values from CLI options and env vars, not to YAML files; our `--attribute` values carry no surrounding quotes and `buildOfficialSite` passes none. Decisive check: I built the official site under both 3.1.12 and 3.2.2 — after normalizing the `<meta name="generator">` tag, **all 3421 pages are byte-identical**. - `setOfficialAntoraYaml`: passes, and is version-independent — a plain Gradle `Copy` that never invokes Antora. - `versionCatalogFormat`: clean. Lunr extension stays at `1.0.0-alpha.10` per @epugh: no compatibility tie to 3.2, and alpha.11–13 are search-behaviour changes deserving their own check. `releaseWizard` end to end is still untested since it commits, pushes and tags — but its only Antora touch points are the two tasks above, both exercised here in the wizard's own configurations. -- 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]
