Closed jaredsburrows closed 1 year ago
v2 / v3 will take the latest of that major version, so this should have no effect. It only pins up to that version, which will create dependabot noise. If pinning for reliability and security, then by hash is ideal even though more annoying. I don't think pinning is needed because these are core actions which will not break, so I think you can drop those changes.
This isn't uploading a release artifact, only test results, so I think you can keep it. I don't see a harm if running on a fork and uploading the outputs for them to debug. They are small so minimal harm and no cache TTL is needed.
...
I guess that means I don't think any of these changes are helpful. Good ideas, but on inspection not very useful? I might be missing something and being dumb, though!
Ok. Will close for now!
@ben-manes
actions/checkout@v3
->actions/checkout@v3.5.0
gradle/gradle-build-action@v2
->gradle/gradle-build-action@v2.4.0
always()
, let's use a real conditiongithub.repository == 'ben-manes/gradle-versions-plugin' && github.ref == 'refs/heads/master'
and remove the warning. Let it fail if there are no artifacts. Also, only publish on the master branch.