Another question: do we just pin to @master? This would introduce some risk of an action in the future breaking our workflow, but on the upside, never having to go through this process again really.

Another question: do we just pin to @master?

I'm personally fine sticking with our current mode of operation. The major updates to these actions don't seem to happen that frequently so updating once in a while as we have been doing is fine IMO.

@MicahGale if you want to remove the draft status on this PR, I think it's ready to go.

@paulromano There's still a dozen docker workflows to update. I was going to make a patch and try applying it to all docker files and see how that goes.

@paulromano on next release could you remember to check for any warning logs in the deploy CI?

I noticed we make use of coverallsapp/github-action@master near the bottom of in the Ci.yml and this results in a node 16 warning.

perhaps this could also be updated to version 2.2.3 or simply 2

https://github.com/coverallsapp/github-action

So the issue here is that coveralls has a main and master branch, and only deploys to main. So I think using a specific version will be more consistent.