Update labeling action to support pull requests - #48733
Merged
Merged
Conversation
Michael Jolley (michaeljolley)
requested a review
from Dustin L. Howett (DHowett)
June 18, 2026 23:13
Dustin L. Howett (DHowett)
approved these changes
Jun 18, 2026
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
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.
This pull request updates the
auto-labeler.ymlGitHub Actions workflow to improve reliability and maintain compatibility. The most important changes are an upgrade to theactions/github-scriptversion and improved error handling when applying labels, ensuring the workflow does not fail due to restricted permissions.Dependency upgrade:
actions/github-scriptfrom version 7 to version 9 in theApply area labels with AIstep, ensuring continued support and access to the latest features and security updates.Error handling improvements:
try/catchblock around the label application logic to gracefully handle cases where the workflow lacks permission to write labels (e.g., due to restricted integration tokens), logging a message and skipping the operation instead of failing the entire workflow.