Skip to content

release: prepare winTerm 1.3.0-alpha4 prerelease - #37

Merged
HelloThisWorld merged 1 commit into
mainfrom
release/v1.3.0-alpha4
Aug 4, 2026
Merged

release: prepare winTerm 1.3.0-alpha4 prerelease#37
HelloThisWorld merged 1 commit into
mainfrom
release/v1.3.0-alpha4

Conversation

@HelloThisWorld

Copy link
Copy Markdown
Owner

Summary

Prepares the winTerm 1.3.0-alpha4 prerelease. The three alpha3
field-report fixes are already on main through #36; this PR only moves the
release metadata.

Merging this and then pushing tag v1.3.0-alpha4 will run the full release
workflow and publish a GitHub prerelease with Setup EXE and Portable ZIP.

Latest is protected. The release workflow marks any channel other than
stable with --prerelease --latest=false, so /releases/latest keeps
resolving to v1.2.0. This alpha is deliberately not listed on
winterm-site and not submitted to WinGet.

Detailed changes

Field alpha3 alpha4
applicationVersion / tag 1.3.0-alpha3 1.3.0-alpha4
packageVersion 1.3.0.2 1.3.0.3
modulePrerelease alpha3 alpha4
moduleVersion 1.3.0 1.3.0 (unchanged)
channel alpha alpha (unchanged)

Surfaces moved together: version.json, shell/shared/version.json,
ReleaseMetadata.h, MSIX manifest, the three .rc scripts, the module
manifest, 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-alpha4.md documents the three fixes in a "Changes since
alpha3" section — including the note that an antivirus engine may need its
cached verdict cleared for the old module file — plus the unsigned Setup EXE
disclosure. Force-added because .gitignore ignores docs/releases/*.

Validation performed

Environment: Windows 11 Pro 26100, MSVC 14.44.35207, Windows SDK 10.0.26100.0.

Repository scripts — ran, passed

Command Result
verify-version.ps1 PASS — 1.3.0-alpha4 / 1.3.0.3 / 1.3.0+alpha4, channel alpha
verify-branding.ps1 -ExpectedPublisher 'CN=helloThisWorld' PASS
test-release-workflow.ps1 PASS
test-ci-classification.ps1 PASS
test-command-timeline.ps1 PASS
test-visual-progress.ps1 PASS
test-privacy.ps1 PASS
test.ps1 -Suite Smoke -Configuration Release -Platform x64 PASS

Staticgit diff --check clean.

Not run, with reason — compiled tests: no source change in this PR (the
fixes were built and tested in #36: Control CommandTimelineTests 44/44 on a
fresh 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-site is untouched.

Checklist

  • The change is focused and does not include unrelated formatting.
  • Tests were added or updated where appropriate.
  • All tests claimed above actually ran and passed.
  • User-facing behavior and limitations are documented in this repository.
  • This source/docs commit updates the root CHANGELOG.md.
  • The Wiki Development-Changes.md ledger has been pushed with the final source SHA, link, summary, and checkpoint/release.
  • Documentation screenshots reuse a suitable existing sanitized winterm-site asset, or no screenshot was added.
  • Version or schema changes include compatibility and migration notes.
  • Package identity, winterm.exe, and Microsoft Terminal coexistence remain isolated.
  • No command text, terminal output, clipboard content, credentials, or private paths are logged.
  • New source and script files contain the appropriate MIT license header.
  • I did not include generated build output, secrets, certificates, or local absolute paths.

Source ↔ Wiki mapping

Source commit Wiki commit Wiki pages
a98c3e9 3fa753c Development-Changes, Changelog

Boundary

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-site change. No WinGet submission. Latest
stays v1.2.0.

Next step after this merges: push tag v1.3.0-alpha4 to trigger the release
workflow. Beta and the website download slot come after alpha4 passes local
testing.

Promotes the three alpha3 field-report fixes, already on main through pull
request #36, to a fourth installable alpha. This commit only moves the
release metadata.

- Set application version 1.3.0-alpha4, PowerShell module prerelease suffix
  alpha4, and tag v1.3.0-alpha4. The channel stays alpha, and the module
  version stays 1.3.0.
- Advance the package/file version to 1.3.0.3 across the MSIX manifest and
  the three Win32 resource scripts; the display ProductVersion strings carry
  1.3.0-alpha4.
- 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-alpha4 release notes with a Changes-since-alpha3 section,
  including the antivirus-verdict-cache 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.
@HelloThisWorld
HelloThisWorld merged commit c089cae into main Aug 4, 2026
5 checks passed
@HelloThisWorld
HelloThisWorld deleted the release/v1.3.0-alpha4 branch August 5, 2026 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant