Trying the `mrt release path` seems to be broken?

[raix]

Hi, I normally create tags etc. and only use mrt publish this works okay,

I got alot of packages to manage in the v2 collectionFS project and I thought I would give the mrt release path command a go - but it doesnt work for me.

I get this:

$ mrt release cfs-worker
Adding tag and pushing repo

/usr/local/etc/lib/node_modules/meteorite/lib/atmosphere.js:44
        throw("Tag " + versionName + " doesn't exist in repository, please add
                                   ^
Tag v0.0.3 doesn't exist in repository, please add!

My normal working procedure:

cd path
git tag -a v0.0.1 -m 'Version 0.0.1'
git push origin v0.0.1
cd ..
mrt publish path

I'm considering just writing a script that would do this bulk, we have alot of packages, simply walk all the packages in my package dir - and releasing all packages eg. with prefix cfs- if tags and versions dont match and all is committed - maybe rig this as a git hook?. This could be read as a FR :)

[alanning]

I've had issues where I would end up with a "vundefined" tag in the repo. Not sure if it's the same problem.

I'm away from my computer now so going off memory, but it seems to be something related to which directory I'm currently in when publishing/releasing.

If I am one level up its different than if I'm in the directory I'm trying to release. Don't remember which way is the right way but I think if you do it exactly like the instructions it works.

Sent from my phone

I get this:

$ mrt release cfs-worker Adding tag and pushing repo

/usr/local/etc/lib/node_modules/meteorite/lib/atmosphere.js:44 throw("Tag " + versionName + " doesn't exist in repository, please add ^ Tag v0.0.3 doesn't exist in repository, please add! — Reply to this email directly or view it on GitHub.

[raix]

just made https://www.npmjs.org/package/mrtbulkrelease - I have alot of packages to keep track of, it will save me some time and help keep my packages updated/published.