-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove terminal velocity feature tag from OAuth2Manager APIs, enabling for stable release #5072
Remove terminal velocity feature tag from OAuth2Manager APIs, enabling for stable release #5072
Conversation
…g it for stable release
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is step in pipeline which generate terminvelocity header file from xml in WindowsAppSDK-SetupBuildEnvironment-Steps.yml. What's the plan to remove that?
We will remove .h, .xml and pipeline entry post stable release. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
This PR removes the TerminalVelocity mechanism from the OAuth2Manager API, which was previously used to control its visibility across different release channels (Preview, Stable, Experimental). As the feature is now moving towards broader availability (Preview Release) and no longer needs the experimental feature flagging, we are removing the TerminalVelocity-related checks.
The API has gone through spec-review: #4772
A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.