Tag non-breaking release of BenchmarkTools.jl?

[gdalle]

Since the last release, there have been 3 commits that I deem possibly breaking:

• Automatically create nested BenchmarkGroup on access #309 => makes it easier to overwrite existing benchmark groups without noticing, but arguably this is a bad practice anyway
• Don't tune manually set evals parameter #318 => more likely a bugfix
• don't export leaves #333 => removes an undocumented export so probably ok

In my view, semantic versioning is slightly looser when it comes to dev-facing packages like BenchmarkTools.jl, and so we could tag a non-breaking release. What do other people think?

[gdalle]

PS: I tried to maintain this package for a while but I clearly don't have the bandwidth, so once I get those changes release I'll step aside for a good long while

[KristofferC]

removes an #332 (comment) export so probably ok

Looking at https://juliahub.com/ui/Search?q=leaves&type=symbols&u=use I don't see any use of (the relevant) leaves without explicitly using BenchmarkTools prefix.

[gdalle]

then I propose we release 1.4.0

[gdalle]

doing it now since there has not been an objection

[gdalle]

JuliaRegistries/General#96432