Skip to content

Pin Antora to 3.1.10 to fix deploy regression#4155

Merged
kemister85 merged 1 commit into
mainfrom
fix/pin-antora-version
May 28, 2026
Merged

Pin Antora to 3.1.10 to fix deploy regression#4155
kemister85 merged 1 commit into
mainfrom
fix/pin-antora-version

Conversation

@kemister85
Copy link
Copy Markdown
Contributor

@kemister85 kemister85 commented May 28, 2026

Summary

  • Antora 3.1.15 was published on May 26 and introduces a regression where remote content fetching silently produces zero output.
  • The ^3.1.10 range in package.json allows yarn to resolve to 3.1.15 on fresh installs (CI), breaking the deploy workflow.
  • Pins @antora/cli and @antora/site-generator-default to exact version 3.1.10.

Context

Deploy workflow has been failing since May 28 with find: 'build/site': No such file or directory because Antora completes in ~8 seconds without generating any pages.

Test plan

  • Deploy workflow succeeds after merge
  • Local build with pinned 3.1.10 produces full site (1545 pages)

Antora 3.1.15 (published May 26) breaks remote content fetching,
causing the deploy workflow to produce zero output. Pin to the
known-working 3.1.10 release.
@kemister85 kemister85 requested a review from a team as a code owner May 28, 2026 05:24
@kemister85 kemister85 requested a review from MichaelFromin May 28, 2026 05:24
@kemister85 kemister85 merged commit cf417b4 into main May 28, 2026
4 checks passed
@kemister85 kemister85 deleted the fix/pin-antora-version branch May 28, 2026 05:31
kemister85 added a commit that referenced this pull request May 29, 2026
Node 24.16.0 (shipped in runner image 20260525.161.1) causes
isomorphic-git's HTTP transport to silently fail, resulting in
Antora producing zero output. Node 22 LTS is unaffected.

Also reverts the unnecessary Antora version pin from #4155 since
the root cause was Node, not the Antora version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants