Release/v1.3.0 - #49
Merged
Merged
Conversation
… command OSC 133 CommandExecuted published a ShellIntegration/Indeterminate/Running fallback that stayed active until CommandFinished, so any long-running command (k9s, vim, top, FastAPI/uvicorn, Spring Boot, Node dev servers, tail -f, kubectl port-forward) looped the rainbow comet animation for its whole lifetime. The fallback is now a bounded one-shot launch indication scoped by a shell command generation, never by command or process names. CommandExecuted opens a new launch generation and publishes the launch snapshot carrying it; a repeated observation of the same still-running command (alternate screen churn, pane rehydration, reconnect re-broadcast) is idempotent. The renderer bounds the launch with a launch clock: one one-shot compositor animation on a private property set using the existing 1,800 ms IndeterminateCycleDuration (no timer, no polling loop, no CPU frame loop) whose generation-guarded completion asks the state machine to expire the fallback. Expiration clears the stored shell snapshot even while a provider or explicit OSC 9;4 source owns the bar, so a later ownership release cannot resurrect it, and publishes Hidden with Running status so accessibility announces neither a fake success nor a fake cancellation. The launch comet itself plays a single traversal and parks off-track; explicit and provider indeterminate presentations keep the continuous traversal. CommandFinished supersedes the launch immediately and strands in-flight completions, preserving every terminal presentation. Four new TAEF tests cover the one-shot, stale-generation, ownership resurrection, and reset/disable/close invalidation semantics; the source suite locks in the policy, the clock sharing the traversal constant, and the Pane wiring; the smoke fixture gains a long-running one-shot launch and an alternate-screen sequence plus manual guidance for FastAPI, Spring Boot, and k9s. Phase 2 documentation now describes the fallback as a bounded launch indication, and the changelog records the fix under Unreleased.
Third beta of the Command Timeline release, carrying the beta2 field-report fix: the Visual Progress Shell Integration fallback is now a bounded one-shot launch indication, so long-running commands (k9s, vim, top, FastAPI/uvicorn, Spring Boot, Node dev servers, tail -f, kubectl port-forward) no longer animate the rainbow bar forever. Application version 1.3.0-beta3, package/file version 1.3.0.6, PowerShell module 1.3.0 with prerelease suffix beta3, channel beta, tag v1.3.0-beta3. Published as a GitHub prerelease: Latest and WinGet keep pointing at v1.2.0, and the beta is listed on the winTerm website next to the stable download.
Promote the field-tested v1.3.0-beta3 tree to the stable channel on a maintenance branch: application version 1.3.0, package 1.3.0.7, no prerelease suffix, channel stable, ReleaseChannel Stable, tag v1.3.0 across branding, resources, module, and validation literals. Add the 1.3.0 stable release notes (force-added under docs/releases), the CHANGELOG stable entry, and stable README/current-progress pointers. Publishing this tag moves GitHub Latest from v1.2.0 to v1.3.0; main continues separately on the 1.4 series.
HelloThisWorld
marked this pull request as ready for review
August 13, 2026 13:17
Take main (the 1.4 series) for every conflicted version surface and keep only the docs/releases/1.3.0.md stable release notes as this branch's contribution to main. The v1.3.0 tag target (79f4c80) is unaffected; the stable release pipeline builds from the tag, not the branch head.
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
1 participant
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.
Summary
Related issues
Closes #
Detailed changes
Validation performed
List exact commands, environments, results, and any tests that were not available.
Checklist
CHANGELOG.md.Development-Changes.mdledger has been pushed with the final source SHA, link, summary, and checkpoint/release.winterm-siteasset, or no screenshot was added.winterm.exe, and Microsoft Terminal coexistence remain isolated.