`cosmwasm-std` dev-dependency in `cosmwasm-derive` causes `cargo release` to fail

[chipshort]

The problem is:

1. cargo release bumps the version to the not yet released one.
2. cargo publish now seems to require the dev-dependencies to be present:

error: failed to verify package tarball

Caused by:
  failed to select a version for the requirement `cosmwasm-std = "^2.1.0"`
  candidate versions found which didn't match: 2.1.0-rc.1, 2.0.4, 2.0.3, ...
  location searched: crates.io index
  required by package `cosmwasm-derive v2.1.0 (/Users/christoph/Projects/cosmwasm/target/package/cosmwasm-derive-2.1.0)`
  if you are looking for the prerelease package it needs to be specified explicitly
      cosmwasm-std = { version = "2.1.0-rc.1" }
  perhaps a crate was updated and forgotten to be re-vendored?

I see two ways of avoiding this:

1. depend on an older version for the dev-dependency and make sure cargo-release doesn't bump it.
2. get rid of it completely

[webmaster128]

Would this cargo publish option be helpful for the cosmwasm-derive step?

      --no-verify            Don't verify the contents by building them

[chipshort]

Yes, I guess --no-verify will work too, but I don't know if we can apply that on a per-crate basis when using cargo release, so we might have to do it on the full workspace.

[chipshort]

Another option: just mark the examples to not run.