Update sbt-github-actions to 0.14.2

[scala-steward]

Updates com.codecommit:sbt-github-actions from 0.13.0 to 0.14.2.

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

Files still referring to the old version number

The following files still refer to the old version number (0.13.0).
You might want to review and update them manually.

notes/2.0.0-M1.markdown

Ignore future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-github-actions" } ]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, old-version-remains

[milessabin]

LGTM!

[joroKr21]

Is it possible to not rely on the GitHub check names? Every time they change, we can't merge the PR

[milessabin]

Is it possible to not rely on the GitHub check names?

I don't understand that question? Do you mean the ability to bypass the checks? We should have that (I do, and I don't see anything in settings which looks like it would prevent you from bypassing as well).

[joroKr21]

This is what I see, the required checks are no longer there (the name changed)

[milessabin]

@joroKr21 gotcha ... I was expecting you to have the ability to bypass the protection rules.

I've disabled them for now because I can't see an obvious way to grant you that permission.

I attempted to set up a "ruleset" which would allow me to grant that permission to holders of a "Maintain" role, but having done that I couldn't see any way to assign that role to you. Possibly the only way to do this is to set up a team ... I'll look in to that later.

[joroKr21]

Cool, thanks 👍