ci(e2e): commit the rails-mini lockfile - #3074
Merged
Merged
Conversation
solnic
force-pushed
the
e2e/commit-rails-mini-lockfile
branch
from
September 7, 2026 09:57
651de5c to
06d23bc
Compare
solnic
force-pushed
the
e2e/commit-rails-mini-lockfile
branch
from
September 7, 2026 10:57
2a0d519 to
a6003e3
Compare
solnic
marked this pull request as ready for review
September 7, 2026 11:12
sl0thentr0py
approved these changes
Sep 7, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds Gemfile.lock needed by e2e specs so that we won't get unexpected failures by bundling on CI with no lock (which happened with JSON 3.0.0 bump that caused e2e failures).
bin/relockgot support for it too - lemme know if I should separate that into its own PR.#skip-changelog