Closed supervacuus closed 6 months ago
After a short discussion with @kahest, I will maintain the practice of pinning after selecting a version that solves whatever issue a version change should have fixed in the first place (in our case, usually deprecation or bugs). I might even do this for the whitelisted action sources (github
, actions
, getsentry
) in danger
, since getsentry/sentry
even pins those.
see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
In our case, this only affects the following:
The last time I updated, some tool blocked the change due to
codecov
getting an unbounded major version assigned, which seemingly is only allowed foractions/*
- andgetsentry/*
-actions. I hope this time it works sincecodecov
is now a sentry product 😅.skip-changelog