This is mostly a workaround until time::UtcOffset::current_local_offset() is sound again (see https://github.com/time-rs/time/issues/293)
It is sound in our use case (we're single threaded so we can't possibly setenv at the same time as a timezone call), but we're not able to set --cfg unsound_local_offset in all build environments, because crates.io ignores .cargo/config.toml files and build.rs scripts are run after dependencies are compiled.
Once https://github.com/rust-lang/rust/issues/27970 is fixed somehow and propagated out to time (or time has another solution for the problem in it's 293 issue), we can remove this workaround and consume it.
Otherwise this PR sets the clap version from the Cargo.toml version.
This is mostly a workaround until
time::UtcOffset::current_local_offset()is sound again (see https://github.com/time-rs/time/issues/293) It is sound in our use case (we're single threaded so we can't possiblysetenvat the same time as a timezone call), but we're not able to set--cfg unsound_local_offsetin all build environments, because crates.io ignores .cargo/config.toml files and build.rs scripts are run after dependencies are compiled.Once https://github.com/rust-lang/rust/issues/27970 is fixed somehow and propagated out to time (or time has another solution for the problem in it's 293 issue), we can remove this workaround and consume it.
Otherwise this PR sets the clap version from the Cargo.toml version.