Release version 2.7.0

[notgull]

• Replace some async blocks with manual futures (Replace some async blocks with manual futures #34)
• Remove our dependency on futures-lite (m: Remove futures-lite dependency #36)
• Mark guard types with #[clippy::has_significant_drop] (Mark MutexGuard with #[clippy::has_significant_drop] #37)

[notgull]

Whoops, realized that #34 is not a patching change. Let me fix that.

[notgull]

Hmm, does squash merging break the auto-releaser? I guess I have to push again

[taiki-e]

auto-releaser

It rejects tags not available in master.

async-lock/.github/workflows/release.yml

Line 17 in e525424

branch: master

[taiki-e]

Hmm. I noticed Cargo.toml's release guide is from when we were pushing release commits without going through PR. It needs to be updated. The latest version is something like:

• Update version and CHANGELOG.md
• Create PR including the above change
• (once the PR is merged) Create "v2.x.y" git tag on the merged commit and push it (git push origin --tags)
• Run cargo +stable publish (do not use nightly because it is sometimes broken)

[notgull]

Weird; it looks like the merge commit was tagged with 2.7.0. Not sure why that didn't go through?

Anyways, I manually created the release on GitHub and published the new version to crates.io.

[taiki-e]

v2.7.0 tag points to 89f94e7, but it is not included in the master branch.

https://github.com/smol-rs/async-lock/actions/runs/4316235059/jobs/7531735651

The correct commit is e525424 at the head of the current master branch.

[notgull]

Thanks for the explanation @taiki-e! I'll keep this in mind for future releases.