Skip to content

Docs(ci): Publish Kotlin and Scala trees - #40

Merged
tony merged 3 commits into
masterfrom
docs-wrapper-publishing
Sep 28, 2026
Merged

tony merged 3 commits into
masterfrom
docs-wrapper-publishing

Conversation

@tony

@tony tony commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Kotlin and Scala publish their own documentation trees beside Java, from the same source revision and release event. A manual dispatch can select one language or all three. Each language has its own artifact, manifest and publication queue.

Both shared workflows pin the reviewed revision in libtmux/docs#41, including the release-prefix fix from docs #42. The parent AWS role now has the Kotlin and Scala prefix grants; simulations verify the permitted prefixes and denials outside this family.

Validation: actionlint passes. Shared workflow tests cover parent/wrapper expansion and reject a different repository's source ownership. Direct review-agent review found no issues in the caller diff. PR checks build all three languages without publication. All checks pass on the rebased PR head, including the Java, Kotlin and Scala documentation builds and the tmux test matrix.

why: The wrapper libraries share Java's source and releases but need
independent language pages and version manifests on libtmux.org.

what:
- Build all three languages on pushes, tags and pull requests
- Allow a dispatch to select one language at any source ref
- Publish each artifact under its own port and version prefix
- Serialize updates per language and keep workflow pins together
why: Kotlin and Scala publication needs the family workflow and the
corrected release prefix check from the current docs base.

what:
- Keep build and publish on the same reviewed docs revision
@tony
tony force-pushed the docs-wrapper-publishing branch from 470e787 to ad247ab Compare September 27, 2026 23:45
@tony
tony merged commit 273f577 into master Sep 28, 2026
26 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