Publish new versions of cargo-apk to crates.io

[atouchet]

The latest version of cargo-apk on crates.io is 0.4.0 while on GitHub it is now at 0.4.3.

[goddessfreya]

cc @Osspial, shouldn't travis be doing this?

[Osspial]

Huh, it doesn't look like Travis is running at all!

[philip-alldredge]

When this is fixed, android_glue should be published as well.

Do we want to run Circle CI or travis or both?

I noticed that, unlike android_glue, tomaka is the only owner that shows up on crates.io.

The current circle CI is broken so it doesn't update the docker image and it is not configured to attempt the crates.io update.

What would you like to do about the docker image? Fixing the Circle CI config would fix the tomaka/cargo-apk repo. If we want to use that dockerhub repo with travis, then tomaka would need to configure the docker secret. Alternatively, a new dockerhub repo could be setup under the rust-windowing name.

I don't mind the leg work to update travis and/or circle CI config but someone would need to configure the environment variables for dockerhub and crates.io as appropriate once things are building.

CC: @mb64

[mb64]

Issue #202 was about shipping an old version of the compiler in the Docker image. It would be good to have the Docker image automatically rebuild with new Rust releases.

I'm bringing it up here as a related CI problem.

[mb64]

@Osspial (or whoever is in charge of publishing to Crates.io) Would you mind setting up CircleCI (or Travis) to do this?

For CircleCI, it would involve something like publish-to-cratesio: filters: branches: only: master.

[Osspial]

@mb64 Sure thing #247

[Osspial]

Alright, it looks like the main thing blocking this now is that Tomaka hasn't transferred cargo-apk's crates.io ownership to the rust-windowing organization. I've emailed him about that, and once that's resolved this should be good to go 👍.