release: prepare winTerm 1.3.0-beta1 prerelease - #38
Merged
Conversation
Promotes the Command Timeline to its first beta. Feature content is identical to 1.3.0-alpha4, which passed local field testing across four alpha rounds; this commit advances the channel and the release metadata. - Set application version 1.3.0-beta1, channel beta, PowerShell module prerelease suffix beta1, tag v1.3.0-beta1, and package/file version 1.3.0.4 across the MSIX manifest and the three Win32 resource scripts. The About metadata channel moves from Alpha to Beta. - Rewrite the README download and feature sections: the Command Timeline and automatic PowerShell shell integration join the core feature list, and the download section presents the stable channel (Latest, v1.2.0) alongside the beta prerelease. verify-version.ps1 now checks the README source version against release metadata and separately asserts that the stable wording keeps pointing at 1.2.0. - Add the 1.3.0-beta1 release notes covering the full Command Timeline surface, the alpha-series fix history, and the unsigned Setup EXE disclosure. The release workflow marks any non-stable channel with --prerelease and --latest=false, so /releases/latest keeps resolving to v1.2.0. The beta will be listed on the winTerm website next to the stable download; WinGet continues to skip prereleases. Workspace schema, docking model, shell protocol, theme schema, update manifest schema, package identity, and signing policy are unchanged.
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
Prepares the winTerm 1.3.0-beta1 prerelease — the first beta. Feature content is identical to 1.3.0-alpha4, which passed local field testing across four alpha rounds; this PR advances the channel and metadata, and rewrites the README download/feature sections.
Merging this and then pushing tag
v1.3.0-beta1will run the full releaseworkflow and publish a GitHub prerelease with Setup EXE and Portable ZIP.
Detailed changes
applicationVersion/ tag1.3.0-alpha41.3.0-beta1packageVersion1.3.0.31.3.0.4modulePrereleasealpha4beta1moduleVersion1.3.01.3.0(unchanged)channelalphabeta(About metadata channel Beta)Surfaces moved together:
version.json,shell/shared/version.json,ReleaseMetadata.h, MSIX manifest, the three.rcscripts, the modulemanifest, the workspace serializer fallbacks, and the version literals pinned
by the five verification scripts, with the post-bump repository sweep
grepping clean.
docs/releases/1.3.0-beta1.mdcovers the full Command Timeline surface, thekeyboard map, settings, the alpha-series fix history, privacy boundaries, and
the unsigned Setup EXE disclosure. Force-added because
.gitignoreignoresdocs/releases/*.README now leads with the stable (Latest, v1.2.0) and beta download
channels, and the feature list gains the Command Timeline and automatic
PowerShell shell integration.
verify-version.ps1checks the README sourceversion against release metadata generically and separately asserts the
stable wording stays at
1.2.0, so a prerelease bump can never silently movethe recommended download.
Validation performed
Environment: Windows 11 Pro 26100, MSVC 14.44.35207, Windows SDK 10.0.26100.0.
Repository scripts — ran, passed
verify-version.ps1verify-branding.ps1 -ExpectedPublisher 'CN=helloThisWorld'test-release-workflow.ps1test-ci-classification.ps1test-command-timeline.ps1test-visual-progress.ps1test-privacy.ps1test.ps1 -Suite Smoke -Configuration Release -Platform x64Static —
git diff --checkclean.Not run, with reason — compiled tests: no source change in this PR (the
fixes were built and tested in #36: Control
CommandTimelineTests44/44 on afresh build, including the new end-to-end Enter-keypress test). The full
Release build, installer, and packaging run in the tag-triggered release
workflow, which is the authority for them.
No screenshot was needed or created.
winterm-siteis untouched.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.Source ↔ Wiki mapping
2a72171c1fee5cBoundary
Workspace schema (2), docking model (1), shell protocol (1), theme schema (1),
update manifest schema (1), package identity, and signing policy are unchanged.
No feature code changes. No
winterm-sitechange. No WinGet submission. Lateststays v1.2.0.
Next step after this merges: push tag
v1.3.0-beta1to trigger the releaseworkflow. Beta and the website download slot come after alpha4 passes local
testing.