Keep fixture Gemfiles in sync when bumping version #8869
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This super simple change actually caught a truffleruby specific regression. Working on it at #8872. |
deivid-rodriguez
force-pushed
the
deivid-rodriguez/keep-fixture-gemfiles-in-sync-too-when-bumping-version
branch
from
56b894d to
781443c
Compare
deivid-rodriguez
deleted the
deivid-rodriguez/keep-fixture-gemfiles-in-sync-too-when-bumping-version
branch
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 4, 2025
…gemfiles-in-sync-too-when-bumping-version Keep fixture Gemfiles in sync when bumping version (cherry picked from commit 629c867)
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 9, 2025
…gemfiles-in-sync-too-when-bumping-version Keep fixture Gemfiles in sync when bumping version (cherry picked from commit 629c867)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the end-user or developer problem that led to this PR?
Not much, it just seems nice that all lockfiles in our repo lock the current development version of Bundler.
What is your fix for the problem, implemented in this PR?
Include fixture lockfiles in the task that bumps locked version of Bundler.
Make sure the following tasks are checked