Bump github/issue-labeler from 2.6 to 3.0

[dependabot]

Bumps github/issue-labeler from 2.6 to 3.0.

Release notes

Sourced from github/issue-labeler's releases.

v3.0

What's Changed

Breaking change: Issue labels that do not match a regex will no longer be removed by default unless you set sync-labels: to 1

• feat: add sync-labels option by @​balazsorban44 in github/issue-labeler#59

Full Changelog: github/issue-labeler@v2.6...v3.0

Commits

• cd54a96 fix for 3.0
• be327c6 feat: add sync-labels option (#59)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Josh-Cena]

I wonder if we should enable the sync-labels option or not... github/issue-labeler#59

[bsmth]

I wonder if we should enable the sync-labels option or not...

From what I gather according to the release notes, it looks like this won't make a difference for us:

Issue labels that do not match a regex will no longer be removed by default

Issues coming from pages are using the issue template, this breaking change will not remove labels by default if someone adds one e.g. from here is that correct?

[caugner]

Issue labels that do not match a regex will no longer be removed by default

@bsmth Based on the changes in the upstream PR, labels are no longer removed if the corresponding regex no longer matches.

Example: Let's say a PR updates a CSS page, then the labeler will assign the Content: CSS label. So far, no change. Now, if the PR is updated to revert the CSS page and update an HTML page, the behavior changes. Previously, it would remove the Content: CSS label and add the Content: HTML label. Now, it only adds the Content: HTML and does NOT remove the Content: CSS label (unless the sync-labels option on the workflow is set to 1/true).

I think we do want to set sync-labels: 1 on the workflow to maintain the previous behavior.

[Josh-Cena]

@caugner AFAICT, this workflow is only used to label issues, not PRs.

[caugner]

AFAICT, this workflow is only used to label issues, not PRs.

You're right, I mixed it up with the PR labeler. I guess issue descriptions change so rarely that it's kind of an edge case, but maybe still worth keeping the previous behavior?

[bsmth]

I think we do want to set sync-labels: 1 on the workflow to maintain the previous behavior.

I'm going to add this to this PR