Check Gemfile.lock and Gemfile.next.lock match on deps update
What does this MR do and why?
This MR adds a check to verify that Gemfile.next.lock
file is up-to-date. When dependencies are updated via renovate, it's ensured by these changes:
- Copy Gemfile.lock to Gemfile.next.lock before l... (gitlab-org/frontend/renovate-gitlab-bot!949 - merged)
- feat: update Gemfile.next.lock and Gemfile.next... (gitlab-org/frontend/renovate-gitlab-bot!913 - merged)
But if the dependency is updated some other way, for example, via a direct push, we need to ensure that Gemfile.next.lock
and Gemfile.next.checksum
are updated as well.
The job:
- Runs
bundle install
forGemfile.next
- It verifies that
Gemfile.next
matchesGemfile.next.lock
- It verifies that
Gemfile.next.lock
matchesGemfile.next.checksum
- It verifies that
- Copies
Gemfile.lock
toGemfile.next.lock
and runsbundle lock
- It will ensure that the minor/patch versions of gems that are not related to next-rails-version are also the same: Copy Gemfile.lock to Gemfile.next.lock before l... (gitlab-org/frontend/renovate-gitlab-bot!949 - merged)
- Runs
bundle install
again to ensure thatGemfile.next.lock
doesn't contain any new dependencies now
Edited by Igor Drozdov