-
Notifications
You must be signed in to change notification settings - Fork 221
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
Fix GitHub Actions failures and add Ruby 3.3 to CI #359
Conversation
Once this gets merged, I can rerun #358 to confirm the fix. |
I think you need to migrate from the archived cookiejar gem to the new cookiejar2 gem. |
…x-ci This merges the contents of igrigorik#359 into our fork, in order to fix the broken GitHub workflows. As mentioned in [1], the Ruby 3.3 build is currently failing; we’ll live with this for now. [1] igrigorik#359 (comment)
I tried running the actions from this branch on my fork and all of the jobs are passing. Has cookiejar been fixed upstream? |
@lawrence-forooghian yes! |
…eate-ably-fork This merges the contents of igrigorik#359 into our fork, in order to fix the broken GitHub workflows.
e940641
to
10a2571
Compare
I just triggered CI again and all jobs are now passing in this PR, even Ruby 3.3, thanks to the cookiejar fix upstream. |
ty sir! |
My initial GitHub Actions CI workflow that I provided in #357 had mistakes that are currently causing it to fail on the master branch.
This PR fixes those failures. I have tested it on my fork, see: https://github.com/mattbrictson/em-http-request/actions/runs/7411502617
The following problems are now fixed:
- uses
typolibcurl4-openssl-dev
dependency so that thecurb
gem buildsfail-fast: false
so that one failing Ruby version in the CI matrix doesn't stop the others from runningI also added Ruby 3.3 to the build matrix.
Note that this version currently fails, due to known issues documented in #358.Now fixed.