Update metadata json in preparation for 6.1 release #7741
Merged
Conversation
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
ReleaseTag is now StableReleaseTag NextReleaseTag is not PreviewReleaseTag Added ServicingReleaseTag for the N-1 Stable release
TravisEz13
requested review from
adityapatwardhan,
anmenaga,
dantraMSFT and
daxian-dbw
as code owners
Contributor
|
Was this already discussed somewhere? Not exactly a lot of time given to assess and remediate dependencies. |
TravisEz13
added a commit
that referenced
this pull request
Sep 10, 2018
ReleaseTag is now StableReleaseTag NextReleaseTag is not PreviewReleaseTag Added ServicingReleaseTag for the N-1 Stable release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR Summary
update metadata json in preparation for 6.1 release
The old names will be removed after we release.
FYI, @DarwinJS in case you use this.
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests