release: prepare winTerm 1.3.0-alpha3 prerelease - #35
Merged
Conversation
Promotes the five alpha2 field-report fixes, already on main through pull request #34, to a third installable alpha. This commit only moves the release metadata. - Set application version 1.3.0-alpha3, PowerShell module prerelease suffix alpha3, and tag v1.3.0-alpha3. The channel stays alpha, and the module version stays 1.3.0. - Advance the package/file version to 1.3.0.2 across the MSIX manifest and the three Win32 resource scripts; the display ProductVersion strings carry 1.3.0-alpha3. - Update the version literals pinned by verify-version.ps1, verify-branding.ps1, test-visual-progress.ps1, test.ps1, and package-shell-assets.ps1. - Add the 1.3.0-alpha3 release notes with a "Changes since alpha2" section covering the five fixes and the antivirus resilience note, and retitle the changelog's unreleased section. The release workflow marks any non-stable channel with --prerelease and --latest=false, so /releases/latest keeps resolving to v1.2.0, the alpha is not listed on the winTerm website, and the WinGet workflow skips it. 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-alpha3 prerelease. The five alpha2 field-report
fixes are already on
mainthrough #34; this PR only moves the releasemetadata.
Merging this and then pushing tag
v1.3.0-alpha3will run the full releaseworkflow and publish a GitHub prerelease with Setup EXE and Portable ZIP.
Detailed changes
applicationVersion/ tag1.3.0-alpha21.3.0-alpha3packageVersion1.3.0.11.3.0.2modulePrereleasealpha2alpha3moduleVersion1.3.01.3.0(unchanged)channelalphaalpha(unchanged)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
verify-version.ps1,verify-branding.ps1,test-visual-progress.ps1,test.ps1, andpackage-shell-assets.ps1(this pass used a sweep that grepsthe repository clean of the previous version literals before the gates run).
docs/releases/1.3.0-alpha3.mddocuments the five fixes in a "Changes sincealpha2" section plus the antivirus resilience note and the unsigned Setup EXE
disclosure. Force-added because
.gitignoreignoresdocs/releases/*.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 #34: SettingsModel winTerm classes 44/44,
Control
CommandTimelineTests43/43 on fresh builds). The full Release build,installer, and packaging run in the tag-triggered release workflow, which is
the authority for them.
test-shell-integration.ps1 -Shell Allremainsblocked locally by antivirus on
Compatibility.ps1; it runs in the releaseworkflow's gates.
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
9f8198ccf9af5cBoundary
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-alpha3to trigger the releaseworkflow. Beta and the website download slot come after alpha3 passes local
testing.