fix: bump version to 0.2.0 for prerelease publishing#13
Merged
Conversation
Prerelease versions (0.1.1-previewN) are semantically LOWER than the release version (0.1.1) already on PSGallery. Bumping to 0.2.0 so develop publishes 0.2.0-previewN which exceeds 0.1.1. Also broadened the skip-duplicate catch pattern to match 'version must exceed' error messages from Publish-Module. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
0.1.1-preview24are lower than0.1.1in SemVer, so PSGallery rejects them with "version must exceed the current version"ModuleVersionto0.2.0so develop publishes0.2.0-previewNwhich exceeds0.1.1version must exceederrorsTest plan
0.2.0-previewNon develop push🤖 Generated with Claude Code