Should I commit a generated .versions file?


#1

After publishing my Meteor package, I noticed that a .versions file appeared.

$ cat .versions 
base64@1.0.3
binary-heap@1.0.3
callback-hook@1.0.3
check@1.0.5
csats:libxmljs@1.0.0
...

Should I commit this file?


".versions" file appeared. Should I track it with git?
What files or folder should be ignored in .gitignore
#2

Yes you should. That file makes sure that meteor builds are repeatable across machines and platforms.

Check the already pre-generated .gitignore file in that directory for files/directories you should not commit.


#3

To clarify, I’m talking about the top-level directory of a Meteor package with binary npm packageshttps://github.com/csats/meteor-npm-libxmljs. The .versions file appeared in the topmost directory after I ran meteor publish-for-arch. There’s no autogenerated .gitignore file in the top-level directory.


#4

Yes. For the same reason as @serkandurusoy already said. :wink:


#5

Sorry, I thought you were referring to the one generated by a meteor project, but the answer is still yes, the .versions file is there to ensure consistency.