search

ewilken / hap-rs

Rust implementation of the Apple HomeKit Accessory Protocol (HAP)
Apache License 2.0
196 stars 33 forks source link

Update num requirement from 0.2 to 0.4 #84

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Updates the requirements on num to permit the latest version.

Changelog

Sourced from num's changelog.

Release 0.4.0 (2021-03-05)

  • Updated num-bigint, num-complex, and num-rational to 0.4.0.
    • Updated to rand 0.8 in num-bigint and num-complex.
    • Rational is deprecated in favor of explicit Rational32 or Rational64.
  • As with prior release bumps, all items exported from num-integer, num-iter, and num-traits are still semver-compatible with those exported by earlier version of num.

Release 0.3.1 (2020-11-03)

  • Updated all sub-crates to their latest versions.
  • Clarify the license specification as "MIT OR Apache-2.0".

Release 0.3.0 (2020-06-13)

All items exported from num-integer, num-iter, and num-traits are still semver-compatible with those exported by num 0.1 and 0.2. If you have these as public dependencies in your own crates, it is not a breaking change to move to num 0.3. However, this is not true of num-bigint, num-complex, or num-rational, as those exported items are distinct in this release.

Enhancements

  • Updates to num-integer, num-iter, and num-traits are still compatible with num 0.1 and 0.2.
  • The "alloc" feature enables bigint without std on Rust 1.36+.
  • The "libm" feature enables Float without std in traits and complex.
  • Please see the release notes of the individual sub-crates for details.

Breaking Changes

  • num now requires rustc 1.31 or greater.
    • The "i128" opt-in feature was removed, now always available.
  • rand support has been updated to 0.7, requiring Rust 1.32.

Contributors: @​cuviper

Release 0.2.1 (2019-01-09)

  • Updated all sub-crates to their latest versions.

Contributors: @​cuviper, @​ignatenkobrain, @​jimbo1qaz

Release 0.2.0 (2018-06-29)

All items exported from num-integer, num-iter, and num-traits are still semver-compatible with those exported by num 0.1. If you have these as public dependencies in your own crates, it is not a breaking change to move to num 0.2. However, this is not true of num-bigint, num-complex, or

... (truncated)

Commits


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)
dependabot[bot] commented 1 year ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.