Zondax / hello-rustee

Apache License 2.0
0 stars 2 forks source link

Bump enumflags2 from 0.7.1 to 0.7.7 in /TEE #17

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps enumflags2 from 0.7.1 to 0.7.7.

Release notes

Sourced from enumflags2's releases.

Release 0.7.7

This release fixes a soundness issue in the make_bitflags! macro. Previously, code like this was accepted:

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test { const C: u8 = 69; }

fn main() { let x = make_bitflags!(Test::{C}); }

Iterating over x would then create values of Test with bit patterns that don't correspond to any of the variants, which is undefined behavior.

This bug has been introduced in 0.7.0, together with the make_bitflags! macro itself.

I don't think it is likely that this was actually present in anyone's code, but in an abundance of caution, I have yanked all affected versions.

RUSTSEC advisory pending.

Release 0.7.6

  • Update to syn 2.0 (thanks to @​mwkmwkmwk)
  • Bump MSRV to 1.56.0 to support the above
  • Update crate metadata to compensate for gender drift :3

Release 0.7.5

BitFlags now implements Display, which only shows the flag list (without the binary representation).

Release 0.7.4

  • Added BitFlags::len, which returns the number of flags set.
  • Added BitFlags::exactly_one, which converts a singleton flag set to the flag. Returns Option::None if the input is not a singleton.
  • The iterator returned by BitFlags::iter now implements ExactSizeIterator and FusedIterator.
  • BitFlags now implements IntoIterator.

Release 0.7.3

  • The code generated by the macro no longer triggers Clippy's use_self lint. To prevent further issues of this kind, Clippy now runs on the test suite in CI, with the pedantic and nursery lints enabled too.
  • Some more functions are marked #[inline] now. This will probably improve downstream performance in non-LTO builds.
  • Some more functions are marked #[must_use] now, at the suggestion of Clippy. If this triggers, your code was probably weird and/or broken, but it's not really a mistake I'd expect anyone to make.
  • Minor documentation improvements.

Release 0.7.2

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/Zondax/hello-rustee/network/alerts).