Closed jecisc closed 7 years ago
I am afraid that not getting back a versionInfo from Pharo could cause additional problems ... specifically I am suspicious that MetacelloToolBox>>updateVersionSpec:fullVersionSpec:updateProjects:updatePackages:visited:updated: will fail ... with that said, I think that this code is only used when using a ConfigurationOf and doing an update, so perhaps with the move towards github based projects this won't be a long term issue ...
@jecisc, @estebanlm fixed this particular bug in PR #448 in a slightly different fashion, along with a set of other issues ...
Cool :)
…deprecation warning when current version is array in Pharo
Related issue: https://github.com/dalehenrich/metacello-work/issues/446