Skip to content

Conversation

@deivid-rodriguez
Copy link
Contributor

What was the end-user or developer problem that led to this PR?

Every time rake releases a new version, our ruby-core CI job starts failing. This is because this job does not use lockfiles because the stable branch of ruby does not use lockfiles.

What is your fix for the problem, implemented in this PR?

I'm trying to fix that at ruby/ruby#13472, but I also realized that if we stop hardcoding the version of rake in our specs, things should work either way.

So that's what this PR does.

This should fix currently failing CI.

Make sure the following tasks are checked

Let them run against the version resolved by the `test_gems.rb` gemfile.

This should fix ruby-core CI job that was broken by the release of rake
13.3.0.
@deivid-rodriguez
Copy link
Contributor Author

deivid-rodriguez commented May 30, 2025

Merging to unblock other PRs!

@deivid-rodriguez deivid-rodriguez merged commit b8418bf into master May 30, 2025
85 checks passed
@deivid-rodriguez deivid-rodriguez deleted the deivid-rodriguez/fix-ci branch May 30, 2025 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants