Publish on crates.io

[EriKWDev]

It would be cool if this could be published on crates.io which is the common way to distribute dependencies for rust/cargo projects.

The old bindings by @code-disaster currently use the sokol name on crates.io, but they have expressed that they would be willing to transfer ownership floooh/sokol#802 (comment)

[floooh]

Would this require some sort of semantic versioning?

IMHO it would make a lot of sense to do the publishing automatically with the binding generation, but this happens on each commit (which would be messy for a properly versioned package but is fine for the other language since they simply live in github repos).

And currently there is also no mechanism in place to assign any sort of version when running the bindings generation CI jobs...

...just some things I've been thinking about but haven't found a nice solution so far :)

[EriKWDev]

I believe that in order to publish a new version of the same crate its version label in Cargo.toml indeed has to be semantically larger than the previous one in accordance with SemVer.

Simply incrementing the patch number would be valid. I don't know if there is a limit as to how large the patch number can become.

https://doc.rust-lang.org/cargo/reference/resolver.html

[code-disaster]

You could try to increment the version's patch level in Cargo.toml during binding generation. I don't think it's a good idea to auto-publish though. If that's even possible, or deemed ok by the Cargo people.

[floooh]

We could also update the sokol-rust github repo on each commit, but trigger crate.io releases 'manually' by pushing a version tag to the sokol-rust repo whenever there's noteworthy changes or bug fixes (a bit of a hassle though and I don't really want to commit to semver versioning of the original sokol headers - especially since each header would actually needs its own version number).

...alternatively: run a weekly or monthly CI job which just bumps the patch version number and publishes on crates.io ;)