Skip to content

Remove Gemfile.lock for Ruby head #226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 10, 2024
Merged

Conversation

andyw8
Copy link
Contributor

@andyw8 andyw8 commented Jan 10, 2024

This will prevent failures such as:

nokogiri-1.16.0-x86_64-darwin requires ruby version < 3.4.dev, >= 3.0, which is
incompatible with the current version, 3.4.0.dev

@andyw8 andyw8 requested a review from a team as a code owner January 10, 2024 15:55
@andyw8 andyw8 requested review from egiurleo and KaanOzkan January 10, 2024 15:55
@andyw8 andyw8 force-pushed the andyw8/rm-gemfile-lock-for-head branch 5 times, most recently from 11a0728 to cdbd144 Compare January 10, 2024 16:14
@andyw8 andyw8 force-pushed the andyw8/rm-gemfile-lock-for-head branch from cdbd144 to 7a31bdd Compare January 10, 2024 16:21
@@ -28,8 +28,8 @@ jobs:
- uses: actions/checkout@v3

- name: Remove Gemfile.lock
if: matrix.os == 'windows-latest' && matrix.ruby == '3.1'
run: rm Gemfile.lock
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was invalid previously because it was removing the wrong lockfile in cases where the gemfile was Gemfile-rails-main. It seems the gemspec entry in the Gemfile wasn't playing well with a Gemfile contained in a subdirectory, so I moved it up to the root.

@andyw8 andyw8 merged commit 86c8ba6 into main Jan 10, 2024
@andyw8 andyw8 deleted the andyw8/rm-gemfile-lock-for-head branch January 10, 2024 16:28
@andyw8
Copy link
Contributor Author

andyw8 commented Jan 10, 2024

@andyw8 andyw8 mentioned this pull request Jan 11, 2024
andyw8 added a commit that referenced this pull request Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants