release: prepare winTerm v1.0.0 stable candidate#6
Merged
Conversation
HelloThisWorld
marked this pull request as ready for review
July 17, 2026 20:23
HelloThisWorld
marked this pull request as draft
July 17, 2026 21:24
HelloThisWorld
marked this pull request as ready for review
July 18, 2026 01:33
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.
Summary
Prepare the repository-side winTerm 1.0.0 Stable candidate without creating a tag or public Release.
Kaname.winTermand remove the upstream Microsoft project-board automation.create prprotocol inAGENTS.md.Related issues
No linked issue. This is the feature-frozen v1.0.0 release-preparation change.
Detailed changes
The previous tree identified itself as a 0.6 beta candidate and had an unsigned beta Draft workflow. It did not provide a protected Stable publication boundary, production publisher injection, signature/timestamp validation, complete asset allowlisting, checksums, SBOM generation, provenance verification, or a truthful final release gate.
The new workflow may prepare an explicitly blocked unsigned Draft when protected signing values are absent. It cannot publish that Draft. Publishing requires the exact tagged commit, a protected non-development publisher, valid trusted and timestamped signatures, complete checksum and package verification, GitHub Attestation verification, and exact clean-machine validation evidence. ARM64 remains excluded unless the same commit has native ARM64 build/install/launch evidence.
This PR intentionally does not create
v1.0.0, a Draft Release, a public Release, WinGet submission, or Stable update manifest. Those actions remain blocked by production signing and runtime acceptance gates.Validation performed
Passed locally:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\winterm\test.ps1 -Suite Smoke -Configuration Release -Platform x64git diff --checkNot available locally:
The Draft PR is expected to run both winTerm validation and the full Windows Debug/Release build/package workflow.
Checklist
winterm.exe, and Microsoft Terminal coexistence remain isolated.