Prepare winTerm 1.3.0-beta2 prerelease - #40
Merged
Conversation
Second beta of the Command Timeline release. It carries the prompt wrapper exit code fix from #39 and is otherwise identical to beta1. - Application version 1.3.0-beta2, package/file version 1.3.0.5, PowerShell module 1.3.0 with prerelease suffix beta2, channel beta. - Version literals moved across the branding metadata, manifests, resource scripts, and the six verification scripts that pin them. - README source version and build examples advanced to 1.3.0-beta2; the stable download reference stays at 1.2.0. - CHANGELOG, current progress, and docs/releases/1.3.0-beta2.md record the beta1 finding and the fix.
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
1 participant
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.
Second beta of the Command Timeline release. Feature content is beta1 plus the prompt wrapper exit code fix (#39); this pull request only moves version surfaces and records the release.
1.3.0-beta2, package/file version1.3.0.5, PowerShell module1.3.0with prerelease suffixbeta2, channelbeta..rcfiles, and the six verification scripts that pin them;git grep -Fconfirms no1.3.0-beta1/1.3.0.4/1,3,0,4literals remain underscripts,src,shell, orcustom.props.1.2.0.docs/current-progress.md, anddocs/releases/1.3.0-beta2.md(force-added) record the beta1 finding and the fix.Local gates: verify-version, verify-branding, test-visual-progress, test-command-timeline, test-release-workflow, test-ci-classification, invoke-visual-progress-smoke, and test-privacy all pass.
After merge: tag
v1.3.0-beta2on the squash commit; the release workflow publishes with--prerelease --latest=false, so GitHub Latest keeps resolving to v1.2.0 and WinGet is not triggered.