Include Gemfile.lock in release preparation commit#1819
Merged
neilvcarvalho merged 1 commit intomainfrom May 4, 2026
Merged
Conversation
bundle install updates Gemfile.lock to reflect the new gem version, but it wasn't being staged before the release commit. This left dirty files that caused the release workflow to fail with "There are files that need to be committed first." Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
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.
Summary
The
bundle installstep in the prepare-release workflow updatesGemfile.lockto reflect the new gem version, but it wasn't being staged before the release commit. This leftGemfile.lockdirty, causing the release workflow to fail with:This PR fixes that by adding
Gemfile.lockto thegit addin the "Push branch and open draft PR" step, and commits the currently staleGemfile.lock(which still referenced6.5.6).