release: prepare winTerm 1.4.0-alpha prerelease - #47
Merged
Conversation
Switch the tree from the 1.3.3 checkpoint to the 1.4.0-alpha integration candidate of the Pane Search release: channel alpha, package 1.4.0.0, module 1.4.0+alpha, executable metadata 1.4, tag v1.4.0-alpha across branding, resources, module, scripts, and validation literals. Add the 1.4.0-alpha release notes (force-added under docs/releases), the CHANGELOG entry, README (EN/JA) prerelease pointers, and the current-progress rewrite. The checkpoint-tag allowlist is unchanged so the v1.4.0-alpha tag runs the full guarded release pipeline.
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.
release: prepare winTerm 1.4.0-alpha prerelease
Summary
Switches the source tree from the
1.3.3engineering checkpoint to the1.4.0-alphaintegration candidate of the Pane Search release, followingthe exact preparation pattern of the v1.3.0-beta3 prerelease (PR #42).
After this merges, pushing the
v1.4.0-alphatag on the merge commit runsthe full guarded release pipeline — x64 Release build with compiled tests,
artifact generation, draft creation, asset re-download and
installer/portable round-trip testing, attestation — and only then
publishes the GitHub prerelease (
--prerelease --latest=false).Latest stays v1.2.0; WinGet is not touched.
Version switch (channel
stable→alpha)applicationVersion1.3.3→1.4.0-alpha;packageVersion1.3.3.0→1.4.0.0;moduleVersion1.3.3→1.4.0withmodulePrerelease/PSData.Prereleasealpha;tag→v1.4.0-alpha;channel→alpha(bothversion.jsonfiles, appx manifest, all three.rcresources in dotted and comma forms,ReleaseMetadata.hwithReleaseChannel L"Alpha", psd1/psm1, Workspace descriptor/serializerfallbacks).
custom.propsexecutable metadata advances to major.minor1.4.verify-version.ps1,test-visual-progress.ps1,package-shell-assets.ps1,test.ps1(including the psd1 prerelease boundary check),
verify-branding.ps1.v1.4.0-alphamust run the full release pipeline, not checkpoint quickvalidation.
Docs
docs/releases/1.4.0-alpha.mdadded (force-added;docs/releases/*isgitignored) — it becomes the GitHub release body and the
winTerm-1.4.0-alpha-release-notes.mdasset.prerelease link at
v1.4.0-alpha(wording updated from the CommandTimeline beta to the Pane Search alpha) and show the new source version;
docs/current-progress.mdreflects the published-alpha state and thePASS→beta / FAIL→1.4.1-alpha flow.
Validation
verify-version.ps1(channel-aware: alpha suffix consistency), fullSmoke suite,
test-release-workflow.ps1,verify-branding.ps1— allgreen locally on this branch.
(Control 89/89, TerminalApp 51/51, SettingsModel 244/244 on v1.3.3,
which this PR does not modify functionally — version metadata only).
After merge
v1.4.0-alphaand push the tag.asset, then publishes the prerelease automatically.
PASS→1.4.0-beta,FAIL→1.4.1-alpha.