You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore: upgdate travelling ruby version
* chore: update bundler
* chore: upgrade to last Travelling Ruby v2.4
Travelling ruby has deprecated support for linux-x86 (x86_64 is still
supported), so that's been removed from the created packages.
The naming convention for the Windows client has also changed, and that's fixed.
* chore: retain old windows package name
Instead of using the changed Traveling Ruby package name for win32 packages, we'll retain the old naming convention to make the packaging simpler for downstream systems.
See #75 (comment)
* chore: Lock json to version in 2.4.10
I don't know how it worked previously, but when building against ruby 2.2, the Gemfile.lock generated includes refernces to json-2.5.1, and bundler was quite happy to find it.
This is extra weird, because json builds native extensions by default, something that doesn't work with cross-platform binaries.
According to https://stdgems.org/2.4.10/, json is still included as a standard gem, but only up to version 2.0.4
When tring to check the created package, it's now failing though.
```shell
$ BUNDLE_GEMFILE=lib/vendor/Gemfile lib/ruby/bin/bundle check
The following gems are missing
* json (2.5.1)
Install missing gems with `bundle install`
```
A solution is to lock the JSON gem at the version provided by Ruby's standard libraries (https://stdgems.org/2.4.10/)
Whether this is still cross-platform (bundler output does report building native extensions) is unknown.
Co-authored-by: Beth Skurrie <[email protected]>
Co-authored-by: Jonathon Padfield <[email protected]>
Co-authored-by: Beth Skurrie <[email protected]>
0 commit comments