build(deps): bump phf from 0.10.1 to 0.11.1

[dependabot[bot]]

Bumps phf from 0.10.1 to 0.11.1.

Release notes

Sourced from phf's releases.

phf v0.11.1

Chore

• point to local crates for now

Documentation

• state allowed key expressions in phf_map

Bug Fixes

• remove now-unnecessary proc-macro-hack crate usage Resolves rust-phf/rust-phf#255.

  This resolves an issue with Windows Defender identifying proc-macro-hack as threats. It also sheds a depedency that is no longer necessary, now that the MSRV of this crate is 1.46 and proc-macro-hack is only useful for providing support for Rust versions 1.31 through 1.45. Per upstream:

  Note: As of Rust 1.45 this crate is superseded by native support for #[proc_macro] in expression position. Only consider using this crate if you care about supporting compilers between 1.31 and 1.45.

Commit Statistics

• 234 commits contributed to the release over the course of 2957 calendar days.
• 3 commits where understood as conventional.
• 1 unique issue was worked on: #249

Commit Details

• #249
  • Add Map::new() function and Default implementation to create new, empty map (baac7d0)
• Uncategorized
  • Replace handmade changelog with generated one by cargo-smart-release (cb84cf6)
  • Add category to crates (32a72c3)
  • Update repository links on Cargo.toml (1af3b0f)
  • Release 0.11.0 (d2efdc0)
  • Merge pull request #257 from JohnTitor/edition-2021 (36ec885)
  • Make crates edition 2021 (b9d25da)
  • remove now-unnecessary proc-macro-hack crate usage (caf1ce7)
  • point to local crates for now (92e7b43)
  • Merge pull request #253 from JohnTitor/action-tweaks (a3e04bc)
  • Fix some Clippy warnings (71fd47c)
  • Make "unicase + macros" features work (11bb242)
  • Prepare 0.10.1 release (4cc8344)

... (truncated)

Changelog

Sourced from phf's changelog.

How to make a new release

Since v0.11.1, this repository uses cargo-smart-release to release crates.

Installation

cargo install cargo-smart-release

Before running cargo-smart-release

If the next version has a major change or bumps MSRV, i.e. it increases a minor version on v0.Y.Z or a major version on vX.Y.Z, update the versions mentioned on the README and doc comments (and CI config if it touches MSRV).

Run cargo-smart-release

First, just run:

cargo smart-release phf phf_codegen phf_generator phf_macros phf_shared

This would show what cargo-smart-release would do, e.g. how it updates the version number, changelog, etc. If you satisfy the output, run:

cargo smart-release -u -e phf phf_codegen phf_generator phf_macros phf_shared

This would make actual releases. -e means that it executes actual releases and -u means that it always updates crates-index. cargo-smart-release also takes care of the Git tags.

After executing it, ensure that all the releases are actually happened and the tags are pushed. If all the things are fine, that's it!

Commits

• 3897b21 Release phf_shared v0.11.1, phf_generator v0.11.1, phf_macros v0.11.1, phf v0...
• 3c6af3f Merge pull request #265 from rust-phf/unpin-criterion
• 27a2ce4 phf_generator: Unpin the criterion dependency
• 97f997d Merge pull request #264 from rust-phf/tweak-changelog
• cb84cf6 Replace handmade changelog with generated one by cargo-smart-release
• d441940 Merge pull request #263 from lopopolo/lopopolo/rand-no-default-features
• deefda1 Disable default features for rand dep in phf_generator
• 1407ebe Merge pull request #260 from JohnTitor/fix-repo-link
• 488b163 Fix a typo
• e0b34fa Add README.md for some crates
• Additional commits viewable in compare view

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)

[niyaznigmatullin]

Right after 0.10.1, in version 0.11 they bumped MSRV to 1.60 https://github.com/rust-phf/rust-phf/commit/11bb2426f0237b1ecea8c8038630b1231ede4871

[niyaznigmatullin]

@dependabot close

[dependabot[bot]]

Sorry, only users with push access can use that command.

[tertsdiepraam]

@niyaznigmatullin Since you've been looking into this, what would be a good MSRV to bump to now that version 0.0.15 has been released? 1.60?

[niyaznigmatullin]

I'm not sure we need 1.60. The problem in phf is that they use optional dependency feature ? syntax, that is available from 1.60.

unicase = ["phf_macros?/unicase", "phf_shared/unicase"]

I think we will be OK with 1.57 for now, we can bump later to 1.60, when we see that it's absolutely necessary.

[niyaznigmatullin]

But after all, I wonder does anyone depend from uutils, is there a reason they can't have Rust 1.60. Because I don't know if they have actual versions when not using rustup as an installation tool for Rust. I see no problem bumping MSRV to 1.60 (or even higher if it would be required) except hypothetical issues users can have not being able to get Rust 1.60.

[tertsdiepraam]

It's not so much about whether someone depends on uutils, but about what compiler is available. Essentially, we have to play nice with distros that ship outdated compilers (e.g. debian) if we want uutils to be available in their package managers.

Edit: That being said, I believe we've been ahead of debian for a while now.

[niyaznigmatullin]

Yes, that's what I also thought about, I tried to "google" for how to install Rust on debian and ubuntu, and both resulted in using rustup.

But now I've looked to what is in apt: for debian is 1.48 stable, and for ubuntu apt install rustc installs 1.59.

But anyway as the compiler's old packages being tested, uutils's old packages would also be tested at the same time, so probably no problem for that, as long as we don't bump it faster than Rust version bumps.

[github-actions[bot]]

GNU testsuite comparison:

GNU test failed: tests/misc/tee. tests/misc/tee is passing on 'main'. Maybe you have to rebase?

[dependabot[bot]]

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. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

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