Skip to content

Conversation

@chenlei-yang
Copy link
Contributor

Description

Change the logic of version bumper, in the old logic it just bumps version but didn't check whether there exist duplicated version in the PSGallery or TestGallery. Now the program can avoid duplicated version and choose a more suitable version as the new bumped version.

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • the markdown help files have been regenerated using the commands listed here

@chenlei-yang chenlei-yang requested a review from wyunchi-ms July 6, 2020 06:08
@wyunchi-ms wyunchi-ms merged commit 372fc58 into Azure:master Jul 9, 2020
litchiyangMSFT pushed a commit to litchiyangMSFT/azure-powershell that referenced this pull request Aug 4, 2020
Change the logic of version bumper  to handle the cases that preview version is confusing.
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.

2 participants