why new version is not published on crates.io

[cstkingkey]

No description provided.

[mw66]

Same question.

the readme.md says:

lazy_static = "1.5.0"

but

$ cargo build
    Updating crates.io index
error: failed to select a version for the requirement `lazy_static = "^1.5.0"`
candidate versions found which didn't match: 1.4.0, 1.3.0, 1.2.0, ...

Can we make a new release? Thanks.

[KodrAus]

Hi @cstkingkey @mw66 👋

We're in a bit of a permissions bind that's keeping new releases from making their way to crates.io.

At the moment @Kimundi is the only owner of this crate, and I'm not currently part of the @rust-lang-nursery/libs team who are also able to push new releases up.

[omarabid]

@Kimundi It'd be great if we can get a new release. Getting deprecated usage warnings with 0.1.4.

[Razorr1996]

Any updates? :)

[mw66]

Hi @cstkingkey @mw66 👋

We're in a bit of a permissions bind that's keeping new releases from making their way to crates.io.

At the moment @Kimundi is the only owner of this crate, and I'm not currently part of the @rust-lang-nursery/libs team who are also able to push new releases up.

@KodrAus can we add a rule that each project has at least two owners to prevent issues like this in the future?

[cuviper]

I am on that team -- @KodrAus if the master branch is ready to publish 1.5.0, I can do that for you.

[Bjohnson131]

Any updates? :)

Until the 1.5.0 version is ready, it seems you can use this in your cargo.toml:

lazy_static = { git = "https://github.com/rust-lang-nursery/lazy-static.rs", branch = "master" }