Move CLI docs release automation into docs - #1744
Open
llewellyn-sl wants to merge 2 commits into
Open
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Aug 14, 2026
llewellyn-sl
requested review from
JaimeSeqLabs,
christopher-hakkaart and
justinegeffen
and removed request for
christopher-hakkaart
August 14, 2026 14:59
llewellyn-sl
marked this pull request as ready for review
August 14, 2026 15:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
tw-jar.jarplatform-cli-docsownership/runbook READMEWhy
The previous workflow called a Gradle metadata task that does not exist on tower-cli
master, so every scheduled update failed. Keeping extraction and generated metadata in tower-cli was also rejected as repository bloat. This makes the released CLI JAR the contract and leaves tower-cli responsible only for sending a small release notification.Impact
After this merges, stable tower-cli releases can produce deterministic draft documentation PRs without checking out tower-cli source or using GitHub Packages. Conceptual inference and examples remain an explicit review step guided by the new skill.
This PR intentionally excludes the generated current-release parity snapshot. That output is in the stacked docs #1745, produced by running this implementation locally against
v0.38.0.Validation
v0.38.0v0.37.0actionlinton both workflows