-
Notifications
You must be signed in to change notification settings - Fork 4
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
Further build issues after latest bundler release #47
Comments
It might be we managed to get past the issue in #44 and now we hit a new issue, but this might have been around for a while and the code just never managed to get here. I'll try taking a quick look again and see if I can track this down as well 😄 |
Give #52 a try? |
@segiddins happy to test, how do I do so? The action fails reliably. |
Thank you for opening #52 @segiddins, I totally missed the checksum was also moved into the parser 🤦 @sfnelson you can test the fix in #52 using the commit sha |
@iMacTia I'm not clear how to use that on GitHub Actions, but I've tested locally and this change does resolve my issue. |
Sorry @sfnelson I forgot @segiddins I managed to give this a go just now by explicitly installing The release worked and I received the email correctly this time, but the action is not completing successfully and still showing the error message in the description of this issue |
Given it's running |
mmmh it might be. When I read the documentation, it seemed like it would only install the gem "if needed", but there's no clear way to tell just by looking at the logs unfortunately. Thank you for the new release, I'll let you know if I still bump into issues on the next Faraday release 👍 |
Similar to #44 (fixed by #46), rubygems-await is not able to detect successful releases in Github actions after the latest release of rubygems.
The await appears to start successfully, then prints a warning about a missing
rename
in fileutils.After this, the build continues to run but never detects the successful release.
See https://github.com/katalyst/tables/actions/runs/9708970325/job/26796749546 for an example.
The text was updated successfully, but these errors were encountered: