[marcoienibot]

Fixes the failure in the release-plz job: https://github.com/rust-lang/log/actions/runs/40667352390/job/122745100514

release-plz runs cargo-semver-checks to work out the next version. cargo-semver-checks builds rustdoc for log with all features enabled. That turns on every max_level_* and release_max_level_* feature at once, and those features are mutually exclusive. The build then stops at the compile_error!s in src/lib.rs:

error: multiple max_level_* features set
   --> src/lib.rs:379:1
error: multiple release_max_level_* features set
   --> src/lib.rs:399:1

This PR adds a release-plz.toml that turns off the semver check for the log package, so release-plz no longer runs cargo-semver-checks and can open the release PR.

[Thomasdezeeuw]

We should fix the feature set instead, see

log/.github/workflows/main.yml

Line 133 in 95918ff

- run: cargo hack test --feature-powerset --exclude-features max_level_off,max_level_error,max_level_warn,max_level_info,max_level_debug,max_level_trace,release_max_level_off,release_max_level_error,release_max_level_warn,release_max_level_info,release_max_level_debug,release_max_level_trace

[marcoieni]

the feature set can't be specified in release-plz today unfortunately. But I'm happy to implement this in the near future if you think it makes sense. Can the maintainers of this crate tell what they think about release-plz/release-plz#2291?

[Thomasdezeeuw]

For the log crate being able to specify the feature set is pretty much a must, I can leave a more detailed comment on release-plz/release-plz#2291 later.

[marcoieni]

Thanks, that would be helpful! In the meantime, let's merge this PR so we unblock CI 👍

[Thomasdezeeuw]

I don't do the releases, so I think @KodrAus is a better reviewer for this.

[KodrAus]

We may find ourselves not being able to use semver checks here anyway, unless we can exempt specific modules. log needs to make its internals public to its macros, but they’re not considered public API and we do make changes to them.