Open kaihendry opened 5 years ago
This is a fundamental problem with this design, yes. I need to figure out a way to determine all the necessary information from just things which are checked in... star.json
, as you mention, is not. The Meteor version is, itself, checked in, but so far as I can determine, there is no way to figure out the appropriate version of Node for a given version of Meteor without downloading the whole tarball.
So to move forward here, what do you suggest I do to start using go-meteor in my CI? Check in ./.meteor/local/build/star.json
?
That's the only option thus far, yes. It's not viable going forward, but it is what is required right now.
I noticed in my local checkout / dev env I have
./.meteor/local/build/star.json
But it's not checked in at https://github.com/unee-t/frontend/tree/master/.meteor and it seems required by your helper. So should https://media.dev.unee-t.com/2019-04-02/star.json be checked in?