Merged
Conversation
cameronmeissner
requested review from
AbelHu,
AlisonB319,
Devinwong,
UtheMan,
anujmaheshwari1,
bravebeaver,
djsly,
ganeshkumarashok,
juan-lee,
junjiezhang1997,
lilypan26,
phealy,
r2k1,
smith1511,
timmy-wright and
zachary-bailey
as code owners
Contributor
|
No changes to cached containers or packages on Windows VHDs |
Devinwong
approved these changes
Apr 25, 2025
djsly
approved these changes
Apr 25, 2025
ganeshkumarashok
pushed a commit
that referenced
this pull request
May 14, 2025
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
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.
What type of PR is this?
What this PR does / why we need it:
this PR aims to address the issue of component update PRs being manually created by component owners not having the "renovate" label, and thus being miss-categorized in AgentBaker release notes, for example: #6204.
to address this issue, this PR adds a new "labeler" workflow which utilizes the node assistant GitHub app alongside the labeler workflow: https://github.com/actions/labeler to automatically add the "components" label to any PR that modifies the contents of components.json. Here's an example of this working in action: #6276
Lastly, this PR adds the "components" label to the "VHD Component Updates" section of the release notes in the release.yaml file, ensuring that all component update PRs are correctly categorized in the release notes regardless of author.
Which issue(s) this PR fixes:
Fixes #
Requirements:
Special notes for your reviewer:
Release note: