Material-ui: Versioning in the next branch

[kof]

Current versions are:

 '1.0.0-beta.1': '2017-01-29T21:14:20.848Z',
 '1.0.0-alpha.1': '2017-01-29T21:34:35.902Z',
 '1.0.0-alpha.2': '2017-02-07T20:02:26.062Z',
 '1.0.0-alpha.3': '2017-02-12T21:55:22.047Z',

Beta version is older than the latest alpha. The problem is that beta is higher than any alpha by semver. Which means that we get a beta version installed if we use a selector like this: ^1.0.0-alpha.1 < 1.0.0.

I think there should be no alpha releases if you released a beta. I think as releases evolve and become more robust after using an alpha u start using beta, then you release a stable. It should be a continuation, not 3 parallel running branches.

[kof]

I see the only way to fix it now is to use beta all the way up, because we can't remove that beta release from npm.

[giuseppeg]

fwiw in order to only get alpha releases we are installing using this version ^1.0.0-alpha.1 <1.0.0-beta

[kof]

Or in other words, how can we select the very latest alpha or beta version?

[Shahrukh-Zindani]

This command npm dist-tag ls material-ui will give you two main versions of material-ui.
The first one will be the latest one and the second one will be the latest version of the next branch.
If you run npm install --save material-ui@next, you should be able to get the latest version of the next branch on your local machine. For some reason beta is not the latest verison right now and 1.0.0-alpha.3 is the latest version right now.

[Shahrukh-Zindani]

To answer your question on how you can switch between different versions of the alpha version and beta version. A command like this would work npm install --save --tag next [email protected]. Specifying the version name is necessary though.

[oliviertassinari]

@kof 1.0.0-beta.1 shouldn't have been published in the first place. The npm CLI fails when I try to unpublish it. I'm gonna open an issue on their side.

[oliviertassinari]

Thanks for reaching out! One of us will get back to you as soon as possible.

[kof]

@Shahrukh-Zindani thanks for the "@next" selector, didn't think of tags, this will work for now!
@oliviertassinari since left-pad npm is immutable, you can't unpublish.

[kof]

I think you have no other choice but to use now beta tags.

[mbrookes]

The npm CLI fails when I try to unpublish it. I'm gonna open an issue on their side.

@oliviertassinari this isn't a bug, it was implemented by design after the left-pad fiasco last year: http://blog.npmjs.org/post/141905368000/changes-to-npms-unpublish-policy

We needed to have deleted it within 24 hours, but it looks like support will help:

"If the version is older than 24 hours, then the unpublish will fail, with a message to contact [email protected].

If you contact support, they will check to see if removing that version of your package would break any other installs. If so, we will not remove it."

[oliviertassinari]

We needed to have deleted it within 24 hours

I have already tried removing it within 1 hour but had the same error, same for @nathanmarks. That's not the first issue I see with the npm cli.

[mbrookes]

Try the support email address?

[oliviertassinari]

Hi Olivier,
Great, I have now unpublished [email protected].

$ npm install [email protected]
npm ERR! notarget No compatible version found: [email protected]
npm ERR! notarget Valid install targets:

[oliviertassinari]

Thanks @npm.