GitHub user ptrdom added a comment to the discussion: Replace sbt/setup-sbt in CI: Coursier or our own install step?
In my projects I had good experience with `coursier/setup-action` (https://github.com/ptrdom/scalajs-esbuild/blob/main/.github/workflows/test.yml#L44-L50), though after I started pinning launcher versions I also moved project's sbt and launcher's sbt management over to Renovate to keep both on the same version - Renovate has custom regex resolution available, I understand that scala-steward cannot do that, Dependabot maybe. I also just noticed that I do not pin `coursier/setup-action` in my projects - should start doing that before it causes me trouble. I would say: 1. Try `coursier/setup-action`, if the stability is not ideal - move to our own script then. 1. For our own script: - Use `actions/cache`. - Figure out a way to automate version updates. If Dependabot cannot do it - that is a very good reason to migrate to Renovate. I bet there are ugly ways to hack together our own script to receive Dependabot updates with dummy/hook projects from which the workflow/script extracts versions, but maybe then it is easier to just migrate to Renovate. 1. I do not have a strong opinion on verification. 1. Implement it on one repo first and observe the stability for a while, if all good - unify the approach on all repos. GitHub link: https://github.com/apache/pekko/discussions/3753#discussioncomment-19441185 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
