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
shards: 0.10.0 -> 0.11.0 #89863
shards: 0.10.0 -> 0.11.0 #89863
Conversation
@NixOS/crystal-lang - we cannot just do this in isolation as it drops compatibility with crystal < 0.34 so we need to introduce 0.10 and 0.11 side by side. |
Yeah, I'm gonna work on Crystal 0.35.0, apparently it already ships with shards now, so we might be able to ignore this entirely? |
OK, I probably misread what |
So the new lock format actually is really nice, we can now do offline conversions of locks and with IFD we don't even need |
That said, our new |
Nice!
How about simply slipstreaming the supported shards version into our crystal packages? |
Actually, come to think of it, that's a bad idea. Whatever work goes into it now, is going to be temporary in nature as v1.0 is supposed to launch sometime later this year after which we shouldn't have to care about all these breaking changes. |
Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/crystal-lang/shards/releases.
meta.description for shards is: "Dependency manager for the Crystal language"
meta.homepage for shards is: "https://crystal-lang.org/"
meta.changelog for shards is: ""
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests
, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 0.11.0 with grep in /nix/store/19k4445v57r7l3cb1vb3i9pcy16x8ghs-shards-0.11.0
directory tree listing: https://gist.github.com/043d82a0db0f9722877183319437569b
du listing: https://gist.github.com/e609eb4bc3c68acdad719d75a2e9a16d
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review
12 packages failed to build:
- icr
- mint
3 packages built:
- ameba
- gitAndTools.thicket
- shards
Maintainer pings
cc @peterhoeg for testing.