This is an automated email from the ASF dual-hosted git repository. benweidig pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tapestry-5-site-builder.git
commit 918f7d90246898a8205e83c18830646c1a7eb2a1 Author: Ben Weidig <[email protected]> AuthorDate: Sat Aug 29 12:06:42 2026 +0200 fix(antora): fetch remote content on every build Antora clones the content repositories into its cache and, unless told otherwise, reuses that cache on every later run. On the long-lived CI agent this meant the clone taken when 5.8 was the newest branch was served indefinitely: the 5.9 branch never appeared in the staged site, and rebuilding could not help. Verified against a cache deliberately missing the 5.9 branch: without runtime.fetch the build yields 5.8 as 'current' and cannot resolve the xrefs from main to the new 5.9 pages; with it, the same cache yields 5.9 and builds clean. --- antora-playbook.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/antora-playbook.yml b/antora-playbook.yml index afff903..23da625 100644 --- a/antora-playbook.yml +++ b/antora-playbook.yml @@ -2,6 +2,12 @@ site: title: Apache Tapestry start_page: main::about.adoc +# Antora caches the content repositories below and, by default, reuses that +# cache on every later run. On a long-lived CI agent that means new branches +# and new commits in tapestry-5-site are never seen. Always refetch. +runtime: + fetch: true + content: sources: - url: https://gitbox.apache.org/repos/asf/tapestry-5-site.git
