Skip to content

Conversation

@blueww
Copy link
Member

@blueww blueww commented Sep 30, 2020

Description

Add some breaking change for output type, and remove the before added breaking change warning message
target to 10/27 release.

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

@isra-fel isra-fel self-assigned this Sep 30, 2020
Copy link
Member

@isra-fel isra-fel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally LGTM
You'll need to suppress the detected breaking change errors, see https://github.com/Azure/azure-powershell/blob/master/documentation/Debugging-StaticAnalysis-Errors.md#breaking-changes

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: format

Suggested change
*Removed obsolete property RestorePolicy.LastEnabledTime
* Removed obsolete property RestorePolicy.LastEnabledTime

@isra-fel
Copy link
Member

isra-fel commented Oct 9, 2020

Looks like the conflict needs to be resolved from command line

isra-fel
isra-fel previously approved these changes Oct 10, 2020
@isra-fel
Copy link
Member

/azp run azure-powershell - powershell-core

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

@isra-fel isra-fel added Waiting for CI :shipit: Contains Breaking Change This PR contains breaking change and removed needs-review labels Oct 10, 2020
@blueww
Copy link
Member Author

blueww commented Oct 10, 2020

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run azure-powershell - powershell-core

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

@blueww
Copy link
Member Author

blueww commented Oct 14, 2020

/azp run azure-powershell - powershell-core

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

@blueww
Copy link
Member Author

blueww commented Oct 15, 2020

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

wyunchi-ms
wyunchi-ms previously approved these changes Oct 15, 2020
@wyunchi-ms wyunchi-ms merged commit a63303d into Azure:master Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Contains Breaking Change This PR contains breaking change Waiting for CI :shipit:

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants