Update actions/labeler action to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/labeler	action	major	v5 → v7

---

Release Notes

actions/labeler (actions/labeler)

v7.0.0

Compare Source

v6.2.0

Compare Source

What's Changed

Bug Fix

• Improve PR number validation and warning messages in input handling by @​chiranjib-swain in #​939

Dependency Updates

• Bump js-yaml to 4.2.0, apply npm audit fix, and add undici override by @​dependabot in #​943
• Bump @​typescript-eslint/eslint-plugin from 8.59.1 to 8.61.1 by @​dependabot in #​942

Full Changelog: actions/labeler@v6.1.0...v6.2.0

v6.1.0

Compare Source

Enhancements

• Add changed-files-labels-limit and max-files-changed configuration options to cap the number of labels added by @​bluca in #​923

Bug Fixes

• Improve Labeler Action documentation and permission error handling by @​chiranjib-swain in #​897
• Preserve manually added labels during workflow runs and refine label synchronization logic by @​chiranjib-swain in #​917

Dependency Updates

• Upgrade brace-expansion from 1.1.11 to 1.1.12 and document breaking changes in v6 by @​dependabot in #​877
• Upgrade minimatch from 10.0.1 to 10.2.3 by @​dependabot in #​926
• Upgrade dependencies (@​actions/core, @​actions/github, js-yaml, minimatch, @​typescript-eslint) by @​Copilot in #​934

New Contributors

• @​chiranjib-swain made their first contribution in #​897
• @​bluca made their first contribution in #​923
• @​Copilot made their first contribution in #​934

Full Changelog: actions/labeler@v6...v6.1.0

v6.0.1

Compare Source

What's Changed

• Upgrade publish-action from 0.2.2 to 0.4.0 by @​aparnajyothi-y in #​901

New Contributors

• @​aparnajyothi-y made their first contribution in #​901

Full Changelog: actions/labeler@v6.0.0...v6.0.1

v6.0.0

Compare Source

What's Changed

• Add workflow file for publishing releases to immutable action package by @​jcambass in #​802

Breaking Changes

• Upgrade Node.js version to 24 in action and dependencies @​salmanmkc in #​891
  Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. Release Notes

Dependency Upgrades

• Upgrade eslint-config-prettier from 9.0.0 to 9.1.0 by @​dependabot[bot] in #​711
• Upgrade eslint from 8.52.0 to 8.55.0 by @​dependabot[bot] in #​720
• Upgrade @​types/jest from 29.5.6 to 29.5.11 by @​dependabot[bot] in #​719
• Upgrade @​types/js-yaml from 4.0.8 to 4.0.9 by @​dependabot[bot] in #​718
• Upgrade @​typescript-eslint/parser from 6.9.0 to 6.14.0 by @​dependabot[bot] in #​717
• Upgrade prettier from 3.0.3 to 3.1.1 by @​dependabot[bot] in #​726
• Upgrade eslint from 8.55.0 to 8.56.0 by @​dependabot[bot] in #​725
• Upgrade @​typescript-eslint/parser from 6.14.0 to 6.19.0 by @​dependabot[bot] in #​745
• Upgrade eslint-plugin-jest from 27.4.3 to 27.6.3 by @​dependabot[bot] in #​744
• Upgrade @​typescript-eslint/eslint-plugin from 6.9.0 to 6.20.0 by @​dependabot[bot] in #​750
• Upgrade prettier from 3.1.1 to 3.2.5 by @​dependabot[bot] in #​752
• Upgrade undici from 5.26.5 to 5.28.3 by @​dependabot[bot] in #​757
• Upgrade braces from 3.0.2 to 3.0.3 by @​dependabot[bot] in #​789
• Upgrade minimatch from 9.0.3 to 10.0.1 by @​dependabot[bot] in #​805
• Upgrade @​actions/core from 1.10.1 to 1.11.1 by @​dependabot[bot] in #​811
• Upgrade typescript from 5.4.3 to 5.7.2 by @​dependabot[bot] in #​819
• Upgrade @​typescript-eslint/parser from 7.3.1 to 8.17.0 by @​dependabot[bot] in #​824
• Upgrade prettier from 3.2.5 to 3.4.2 by @​dependabot[bot] in #​825
• Upgrade @​types/jest from 29.5.12 to 29.5.14 by @​dependabot[bot] in #​827
• Upgrade eslint-plugin-jest from 27.9.0 to 28.9.0 by @​dependabot[bot] in #​832
• Upgrade ts-jest from 29.1.2 to 29.2.5 by @​dependabot[bot] in #​831
• Upgrade @​vercel/ncc from 0.38.1 to 0.38.3 by @​dependabot[bot] in #​830
• Upgrade typescript from 5.7.2 to 5.7.3 by @​dependabot[bot] in #​835
• Upgrade eslint-plugin-jest from 28.9.0 to 28.11.0 by @​dependabot[bot] in #​839
• Upgrade undici from 5.28.4 to 5.28.5 by @​dependabot[bot] in #​842
• Upgrade @​octokit/request-error from 5.0.1 to 5.1.1 by @​dependabot[bot] in #​846

Documentation changes

• Add note regarding pull_request_target to README.md by @​silverwind in #​669
• Update readme with additional examples and important note about pull_request_target event by @​IvanZosimov in #​721
• Document update - permission section by @​harithavattikuti in #​840
• Improvement in documentation for pull_request_target event usage in README by @​suyashgaonkar in #​871
• Fix broken links in documentation by @​suyashgaonkar in #​822

New Contributors

• @​silverwind made their first contribution in #​669
• @​Jcambass made their first contribution in #​802
• @​suyashgaonkar made their first contribution in #​822
• @​HarithaVattikuti made their first contribution in #​840
• @​salmanmkc made their first contribution in #​891

Full Changelog: actions/labeler@v5...v6.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.
• If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
• If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• vtctl command output order should be stable and awk-able.

[github-actions]

Charts Differences:

Changes in cluster-bootstrap:

Changes in devxp-app:

Changes in devxp-dev:

Changes in devxp-infra:

Changes in tooling:

[github-actions]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.
• If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
• If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• vtctl command output order should be stable and awk-able.