-
Notifications
You must be signed in to change notification settings - Fork 7
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
bump to 1.20.0 node dependencies #20
Conversation
@@ -1,4 +1,4 @@ | |||
resolver: https://raw.githubusercontent.com/input-output-hk/cardano-haskell/da70d67ff662b85e72e1f203defbf5e3028d03cd/snapshots/cardano-1.19.1.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer we commit this file to the repository:
- easier to view/grep the dependencies
- unbreaks
stack2cabal
(currently doesn't handle remote urls inresolver
) - more static than a url
@paweljakubas did you see my comment? |
@hasufell oh, sorry, PR approve went to me and I automatically merge it... Frankly speaking I tried here to comply with practice we use in other repos, like cardano-wallet, cardano-addresses.... Maybe it is good idea to pursue the approach you recommend, first discuss it in our Slack channel, and then adopt in all repos at once to have this level consistency? What do you think? I do not feel expert in those things and always try to comply with pattern used in other repos |
I don't have a strong opinion. I might just fork stack2cabal anyway, since upstream isn't very active. |
I suspect that the real objection to resolver URLs is that stack2cabal doesn't work with them and the other reasons are just padding. |
No description provided.