Automatically create branches that track the latest releases #3549
Conversation
This file contains 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
schmittjoseph
commented
Feb 2, 2023
jander-msft
previously approved these changes
Feb 3, 2023
Co-authored-by: Justin Anderson <[email protected]>
wiktork
reviewed
Feb 3, 2023
jander-msft
approved these changes
Feb 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR introduces automation that will automatically create/update a
shipped/v{major}.{minor}branch each time a release is made. The HEAD of these branches will be the latest shipped commit for that major/minor version. (e.g.shipped/v7.0).The purpose of these branches is to give us an easier mechanism for Component Governance (CG) to identify if a shipping version contains any potential CVEs in its dependencies and notify us accordingly. This will also require an additional small pipeline to register these branches (
shipped/*) with CG but that can be done in a separate PR.Release Notes Entry