Changes appear related to

python-jsonschema/check-jsonschema@64b6ba0#diff-847b5cf820df48bf0feca3b3580c5b827c266cc0923e35c2dd315d9ac1158289R1619

Which disallows extra properties to the workflow_dispatch portion of the on triggers

In both of the indicated files, we have

  workflow_dispatch:
    workflow: "*"

My yaml syntax knowledge is largely based on cargo-culting, so I think it is telling us we should remove the second line, but not sure if the : on the first line also needs to be removed or not... It is a bit odd because the isolated examples just do on: workflow_dispatch, but when there are other triggers it turns into yaml dict, and not sure you can just have the key alone when other fields have sub-entries.

The only key under workflow_dispatch is inputs, so I'm not sure what was going on there before, but the workflow key should go away.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v3.9.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 f5e74e1bd48ba8ba9d420acb9f0dfaa52db25e0b

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #28949: [pre-commit.ci] pre-commit autoupdate'

4. Push to a named branch:

git push YOURFORK v3.9.x:auto-backport-of-pr-28949-on-v3.9.x

5. Create a PR against branch v3.9.x, I would have named this PR:

"Backport PR #28949 on branch v3.9.x ([pre-commit.ci] pre-commit autoupdate)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

OK, probably not worth backporting.