-
Notifications
You must be signed in to change notification settings - Fork 19
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
ruby 2.7 is EOL since 2023-03-31 #1090
Comments
We have two options: If (a) turns out to be significantly easier, it would be good enough from my perspective ... |
It seems indeed that pinning google-protobuf to 3.25.5 (instead of 3.25.6) addresses the build issue. |
3.25.6 has broken the build with a segfault(!). This is the temporary solution for issue #1090. Signed-off-by: Kurt Garloff <[email protected]>
3.25.6 has broken the build with a segfault(!). This is the temporary solution for issue #1090. Signed-off-by: Kurt Garloff <[email protected]>
3.25.6 has broken the build with a segfault(!). This is the temporary solution for issue #1090. Signed-off-by: Kurt Garloff <[email protected]>
* Bump jekyll from 4.3.4 to 4.4.0 Bumps [jekyll](https://github.com/jekyll/jekyll) from 4.3.4 to 4.4.0. - [Release notes](https://github.com/jekyll/jekyll/releases) - [Changelog](https://github.com/jekyll/jekyll/blob/master/History.markdown) - [Commits](jekyll/jekyll@v4.3.4...v4.4.0) --- updated-dependencies: - dependency-name: jekyll dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Pin google-protobuf to 3.25.5 for now. 3.25.6 has broken the build with a segfault(!). This is the temporary solution for issue #1090. Signed-off-by: Kurt Garloff <[email protected]> --------- Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: Kurt Garloff <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Kurt Garloff <[email protected]>
Partially addressed in #1092. |
This means that
Currently we see this:
The text was updated successfully, but these errors were encountered: