release: 1.4.0 - #50
Merged
Merged
Conversation
Cuts the Unreleased section as 1.4.0: the module reads the PowerShell edition once and detects capabilities on the cmdlet, Get-TestEnvironmentRuntime shows the decision and which PowerShell is preferred, and every provider receives one error shape from the HTTP layer on either edition. Minor rather than patch: a new exported command and a changed error shape. The v1.3.1 tag pushed on the merge of #49 failed the workflow's tag check against a manifest that still said 1.3.0, so nothing was published under it.
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.
Cuts the Unreleased section as 1.4.0 with today's date, bumps
ModuleVersionto 1.4.0, and leads the manifest release notes with a 1.4.0 summary in the style of the earlier ones.1.4.0 rather than 1.3.1: the unreleased work adds an exported command,
Get-TestEnvironmentRuntime, and changes the error shape every provider receives from the HTTP layer, which is a minor bump under semantic versioning. Thev1.3.1tag that was pushed on the merge of #49 failed the release workflow's tag check, because that commit's manifest still said 1.3.0; nothing was published and 1.3.1 was never consumed on the Gallery.Once this merges, the release is
git tag v1.4.0 && git push origin v1.4.0on the merge commit. The stalev1.3.1tag points at a commit whose manifest says 1.3.0 and can be deleted withgit push origin :refs/tags/v1.3.1andgit tag -d v1.3.1.Checked:
Test-ModuleManifestreads 1.4.0 and the new release notes; the module contract suite passes (1,192 tests);Publish-Module.ps1 -WhatIfrehearsesTestEnvironment 1.4.0 -> PSGalleryand publishes nothing.