Commit Graph

9 Commits

Author SHA1 Message Date
renovate[bot]
f26dedd7c9 Update dessant/lock-threads action to v4.0.1 2023-06-12 18:22:16 +00:00
renovate[bot]
ec539ea483 Update dessant/lock-threads action to v4 (#2756)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2022-12-04 13:18:49 +01:00
Archi
aaf9cc67b3 Misc
60 days for lock-threads to ensure that issues and PRs get more or less a full month in stable release in case somebody would like to add something to them
2021-12-03 10:51:48 +01:00
renovate[bot]
24c5aa1a92 Update dessant/lock-threads action to v3 (#2417)
* Update dessant/lock-threads action to v3

* Address breaking changes

Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Archi <JustArchi@JustArchi.net>
2021-09-27 23:42:31 +02:00
Renovate Bot
a8f0456f1f Update dessant/lock-threads action to v2.1.2 2021-08-17 11:18:20 +00:00
Archi
05e36b4cb9 CI: Misc 2021-07-10 00:53:34 +02:00
Renovate Bot
25fa116058 Update dessant/lock-threads action to v2.1.1 2021-07-09 20:07:46 +00:00
Archi
2f7478b968 CI: Pin versions
While floating tags are nice to use and fancy, we already had situations where the fixed source code did not result in the same deterministic build as the one built e.g. a week ago due to non-pinned versions that resulted in a different set of dependencies than originally.

Since GitHub actions follow similar pattern, we want to do our best to ensure that if CI in given fixed version passed on a fixed source, then it should also result in the same deterministic output. Of course this is impossible to achieve in 100% (e.g. resources no longer being available over the network), but this is something we can do.

It wasn't like that before renovate since we didn't have a standarized bot that could handle bumping those versions for us.
2021-06-30 16:19:41 +02:00
JustArchi
454e69b144 Misc 2021-01-01 15:57:19 +01:00