upgrade to Safe.Meta 5.1.0 #632
Conversation
There was a problem hiding this comment.
You don't need to change these lines. ~> means "compatible with", so ~> 5 is fine.
See https://fsprojects.github.io/Paket/nuget-dependencies.html#Pessimistic-version-constraint.
There was a problem hiding this comment.
Ah crap, I was afraid of that... that means ppl are going to have unexpected breaking changes when they update their packages on SAFE 5.x apps. Perhaps we should release a 5.1.1 of the meta packages and revert those breaking changes? Then we could release them as 6.0.0, paired with SAFE.Template 6.0.0?
There was a problem hiding this comment.
Hmm yeah good point 🫤 What do you reckon about a 6.0 release @isaacabraham?
There was a problem hiding this comment.
If we don't want a v6 template release, we could break the synchronisation with metapackages.
|
Hmm. I'll be honest - I'm really not that fussed about a minor breaking change like this. I suppose we could work around it by changing the name of the union case to e.g. The number of people that are aware of and using SAFE.Meta types since we've released it will be very small, I think. As long as we add some decent docs (that we can add to the /// comments) I think that that's acceptable. |
4 participants
Upgrade to use SAFE.Meta 5.1.0
Closes #631