chore(ci): better lockfiles updates#1087
Conversation
df76ff3 to
fed6bd3
Compare
02bd04d to
645a6c5
Compare
| # The smart bump runs the full test suite (including integration tests) to verify | ||
| # each update, and may bisect dependency-by-dependency on failure, so it needs a | ||
| # much larger budget than a blunt `mix deps.update --all`. | ||
| timeout-minutes: 120 |
There was a problem hiding this comment.
FYI that's a pessimistic timeout. During testing it finished in about 40 minutes.
645a6c5 to
0155509
Compare
|
@solnic can you elaborate on why this is necessary? |
|
@whatyouhide we run automatic lock bumps every Monday now (ie see #1091) and tracking down which bump broke what is a bit of a chore, so I wanted to add a tool that could help. I do understand this is a bit too big, so I'm gonna close it for now and use it myself to see how it goes in practice. Maybe we could revisit it later as a potential addition to the repo. /cc @sl0thentr0py |
|
@solnic I think I’m a bit more confused about why we run automatic lock bumps every Monday 😄 Nothing uses the |
|
supply chain hardening because of recent attacks in package ecosystems, its for us, not our users |
This adds an internal
mix sentry.bump_lockfilesmachinery that can perform safe dep version bumps that check our test suites.Here's a sample run:
You can also narrow it down ie: