Error while using fluid-publish to publish a dev version of Infusion

[Clark, Colin]

Hey Justin,

On Oct 23, 2015, at 10:21 PM, Justin Obara <obara.justin at gmail.com<mailto:obara.justin at gmail.com>> wrote:

In regards to the extra “-dev” that’s because the fluid-publish will add the pre-release version based on the “devTag” option.
https://github.com/fluid-project/fluid-publish/blob/master/README.md#dev This means that the version in Infusion will need to be changed to a full release version number. I had talked to Antranig about this in the channel. It was decided that the package.json is expected to contain the version of the next stable release.
https://github.com/fluid-project/fluid-publish/pull/1#discussion_r42398535

Okay, good to know. I'll go ahead and make a pull request to change the version from 2.0.0-dev to 2.0.0.

I’m not exactly sure about the issue with the dist-tag. Which version of NPM are you running?

I'm running npm 2.14.7.

Could you try to manually run this command and see if it works.
"npm dist-tag add infusion at 2.0.0-dev-dev.20151024T010910Z.d1e5b8d dev”

Actually, I think I have an idea of what’s wrong. If the above works, I think there may be a newline character after the commit hash that is causing the problem. If you see your log below, the “dev” tag comes on a separate line from the rest of the command.

Yup, that command worked fine. So is there a stray line break somewhere in our code? Or was it something I did when I published?

Thanks again for helping with this!

Colin

---
Colin Clark
Lead Software Architect,
Inclusive Design Research Centre, OCAD University
http://inclusivedesign.ca


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20151024/49664c77/attachment.html>