Repository navigation
ci(docs) Read final release tags as stable - #86
Merged
Merged
Conversation
what: - Read a package version or release tag as stable when it is exactly MAJOR.MINOR.PATCH, with an optional v and package label, so a final release such as v0.1.0 gets a stable badge instead of throwing, and word the stable badge line "Stable release." without naming a registry; a declared stage and a stable registry status still outrank the name - Read the whole info string of a code fence in the API doc comments of Java, Kotlin and Scala (the java caller builds all three), and hide rustdoc's leading `# ` lines only in Rust examples, so comments in shell, Python, Ruby and YAML examples stay visible - Julia only: build the Julia port's docs with tmux 3.7c, the version Julia requires, compiled by the `build-tmux` command of the Julia checkout's matrix tool and put on PATH only after that build succeeds - Julia only: show the Julia core, workspace and MCP install commands for the documented source revision when the build selects one and for the default branch otherwise, and state Julia 1.13.1 and tmux 3.7c or newer as the floor - Julia only: pass the Documenter `@raw html` blocks of the Julia guides through as page HTML with their `../source/` links rewritten to the documented revision on GitHub, and keep the explicit API references and overviews of those guides inside the selected preview version why: Go example pages opened on a whole program with no path from the tmux commands to the code that runs them. The API extraction of the TypeScript, Rust, Java, Kotlin, Scala and Swift references dropped the `#` comment lines of shell, Python, Ruby and YAML examples in doc comments as if they were rustdoc setup lines. Swift reference signatures printed their parameter list twice, Ruby and Swift type keywords showed as unresolved type names, and the publisher refused the PowerShell port's .NET alpha.22 dependency against its alpha.20 navigation pin. The stage resolver threw on the final release tag v0.1.0 of libtmux-julia. Shared source: libtmux/docs From: 4e891632a66a144bd9dd7747168cf9218eb32710 To: de7abd597bd9205c54d01498d8cdcb0bb0ec37d9
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.
Pin only the shared port builder and publisher to
de7abd597bd9205c54d01498d8cdcb0bb0ec37d9from4e891632a66a144bd9dd7747168cf9218eb32710. All other workflow bytes, library contents, triggers, permissions and language/source/version inputs remain unchanged.Go example pages now lead from the concept to the finished program in small steps. Each step quotes a range of lines of a Go program that a test or a recorded run checks, the steps name the tmux commands behind the calls, the pages link the native shell example they parallel, and the complete program follows the steps. The Go attach page is built on the pane-io example, which types into a pane through an io.Writer and reads what it prints through an io.Reader. The API doc comments of the TypeScript, Rust, Java, Kotlin, Scala and Swift references keep the
#comment lines of shell, Python, Ruby and YAML examples and hide rustdoc's setup lines only in Rust examples. Swift callables are declared by their base name, Ruby and Swift type keywords are drawn as syntax, and the PowerShell reference follows its .NET dependency to LibTmux 0.0.0-alpha.22. A version or release tag that is exactly MAJOR.MINOR.PATCH, such as Julia's v0.1.0, now reads as a stable badge instead of throwing and the stable badge line no longer names a registry.Julia only: the Julia docs build compiles tmux 3.7c, the Julia install commands name the documented source revision and state Julia 1.13.1 and tmux 3.7c or newer as the floor, and the Julia guides keep revision-bound source links and API references inside the selected preview.
The exact required CI and root merge receipts of the shared checkpoint must be verified before this operator runs. This PR does not claim an owner build or publication pass. Root reviews this exact caller diff, actual repository-required checks and reviews before merge; optional native estate checks are not a new universal gate.
Execution route:
controlled_real_pin_merge_push. Root separately schedules reviewed merges and exact source requests from the actual workflow state. If the current active workflow already publishes the intended source on merge, retain that actual event and do not issue a duplicate request. Future source/native/run identities will be bound to actual events.