ramsey / composer-install

:gift: A GitHub Action to streamline installation of PHP dependencies with Composer.
MIT License
233 stars 32 forks source link

GH Actions: version update for codecov action runner #226

Closed jrfnl closed 2 years ago

jrfnl commented 2 years ago

Description

Yet another predefined action has had a major release.

This is, again, mostly just a change of the Node version used by the action itself (from Node 12 to Node 16).

Refs:


@ramsey As an alternative to these kind of (manual) PRs, I'd be happy to add a Dependabot configuration which will create these type of PRs automatically.

Motivation and context

General maintenance.

How has this been tested?

Will automatically be tested via the GH Actions run.

Types of changes

PR checklist

codecov[bot] commented 2 years ago

Codecov Report

Merging #226 (4f754e8) into v2 (e3612f6) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##               v2     #226   +/-   ##
=======================================
  Coverage   98.29%   98.29%           
=======================================
  Files           5        5           
  Lines         117      117           
=======================================
  Hits          115      115           
  Misses          2        2           
ramsey commented 2 years ago

As an alternative to these kind of (manual) PRs, I'd be happy to add a Dependabot configuration which will create these type of PRs automatically.

Yes, please! 😄

@Ocramius added this to ramsey/uuid, and I was going to try to see if it would work here, too, but I hadn't gotten to it, yet. I appreciate your help! https://github.com/ramsey/uuid/blob/4.x/.github/workflows/merge-dependabot-upgrades.yml

jrfnl commented 2 years ago

@ramsey Looks like what @Ocramius added is not the actual configuration, but a way to automatically merge the pull requests from Dependabot. I'm a bit wary of automated merges, so let me for now just pull the config for you and then you can decide on the auto-merge workflow separately.

jrfnl commented 2 years ago

@ramsey See PR #227

Ocramius commented 2 years ago

I'm a bit wary of automated merges,

Mostly depends on test confidence - not viable on some projects, but if you have a very detailed QA suite, you can do this.

jrfnl commented 2 years ago

@Ocramius Hear hear! Unfortunately the majority of projects I work on does not have that, so yeah.