Skip to content

Docs(ci[deploy]): Publish each release's docs from source - #39

Merged
tony merged 1 commit into
masterfrom
docs-versioned
Sep 27, 2026
Merged

tony merged 1 commit into
masterfrom
docs-versioned

Conversation

@tony

@tony tony commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Part of libtmux/docs#27. libtmux.org serves one tree for this port, latest, rendered from the API model libtmux/docs last committed rather than from this repository's source. No release can be read on its own. This follows libtmux/libtmux-rs#37.

What it publishes

  • master → /en/java/latest/. It is the default until the first stable release, and after that stable is.
  • Each v* tag → /en/java/<version>/, plus an alias: next for a prerelease, stable (the default) for a release.
  • Pull requests build latest at their merge commit and publish nothing.

How

  • The build is libtmux/docs's port-docs.yml (Build any port's versioned docs from its source docs#36). It decides the versions from the event, verifies the selected commit, and regenerates the API reference from it. Publishing is its reusable-deploy.yml. Both are pinned to one libtmux/docs commit, and this repository holds no second pin.
  • workflow_dispatch inputs (source-ref, version, version-kind, is-default, resolves-to, publish) publish any ref on demand.

The docs environment admits master and v* tags only (infrastructure Terraform, applied), and the port role trusts only reusable-deploy.yml by its job_workflow_ref claim.

Merge after libtmux/docs#36. The pin is that PR's head commit, which its merge commit keeps in libtmux/docs main's history.

why: libtmux.org served one tree for this port, latest, rendered from
the API model libtmux/docs had last committed rather than from this
repository's source, and no release could be read on its own.

what:
- Publish latest from master, and each v* tag as its own version plus
  an alias: next for a prerelease, stable (the default) for a release
- Accept workflow_dispatch inputs (source-ref, version, version-kind,
  is-default, resolves-to, publish), so any ref can be published on
  demand
- Build through libtmux/docs's port-docs.yml, which regenerates the
  reference from the selected commit, and publish through its
  reusable-deploy.yml, both pinned to one commit
- Build pull requests at their merge commit without publishing, and
  queue only the publish job, so a pull request never delays a deploy
@tony
tony merged commit 3e5b20d into master Sep 27, 2026
24 checks passed
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.

1 participant