Create a new release

[jjpe]

Summary

I need to try out the raw_module functionality because of an issue I outlined here.
So I just tried to use this crate as a git dependency in my project's Cargo.toml, but that results in errors being spewed:

j@lear $ cargo update
    Updating crates.io index
    Updating git repository `https://github.com/jjpe/stringify.git`
    Updating git repository `https://github.com/rustwasm/wasm-bindgen`
    Updating git repository `https://github.com/jjpe/chrono`
    Updating git repository `https://github.com/jjpe/tempus_fugit`
error: failed to select a version for `wasm-bindgen`.
    ... required by package `js-sys v0.3.0`
    ... which is depended on by `sbr-xquery-interpreter-api v0.9.0 (/home/j/dev/accept/quip)`
    ... which is depended on by `sbr-validate-npm v0.9.0 (/home/j/dev/accept/sbr-validate-npm)`
versions that meet the requirements `^0.2.23` are: 0.2.39, 0.2.38, 0.2.37, 0.2.36, 0.2.35, 0.2.34, 0.2.33, 0.2.32, 0.2.31, 0.2.30, 0.2.29, 0.2.28, 0.2.27, 0.2.26, 0.2.25, 0.2.24, 0.2.23

the package `wasm-bindgen` links to the native library `wasm_bindgen`, but it conflicts with a previous package which links to `wasm_bindgen` as well:
package `wasm-bindgen v0.2.39 (https://github.com/rustwasm/wasm-bindgen#d49d8c9e)`
    ... which is depended on by `sbr-validate-npm v0.9.0 (/home/j/dev/accept/sbr-validate-npm)`

failed to select a version for `wasm-bindgen` which could resolve this conflict

Because of this I request a new wasm-bindgenrelease.

Additional Details

Tried to use the master branch as a git dependency but that doesn't work. Therefore a new release is necessary I believe.

[alexcrichton]

Sure thing! This is being done in #1381