Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update async-lock requirement from 2.8 to 3.3 #23

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Mar 27, 2024

Updates the requirements on async-lock to permit the latest version.

Release notes

Sourced from async-lock's releases.

v3.3.0

  • Add a forget() method for semaphore guards. (#73)
  • Increase MSRV to v1.60. (#75)
Changelog

Sourced from async-lock's changelog.

Version 3.3.0

  • Add a forget() method for semaphore guards. (#73)
  • Increase MSRV to v1.60. (#75)

Version 3.2.0

  • Add missing methods for blocking on locking with types wrapped in Arc (#71).

Version 3.1.2

  • Bump event-listener to version v4.0.0. (#69)

Version 3.1.1

  • Add a note to the documentation comparing this crate against libstd's locks. (#58)

Version 3.1.0

  • Add a Default implementation for OnceCell (#63).

Version 3.0.0

  • Breaking: Add an enabled-by-default std feature that allows using this crate without the standard library. (#43)
  • Support blocking and non-blocking operations on the same locks. (#56)
  • Switch to a more efficient event notification mechanism. (#43)

Version 2.8.0

  • Fix a bug where the SemaphoreGuard::acquire_arc future would busy wait under certain conditions (#42).
  • Add a Semaphore::add_permits() function to increase the number of available permits on the semaphore (#44).
  • Make RwLockReadGuard covariant over its lifetime (#45)
  • Add RwLockReadGuardArc, RwLockWriteGuardArc, and other reference counted guards for the RwLock type (#47).
  • Loosen the Send/Sync bounds on certain future types (#48).
  • Fix UB caused by the MutexGuardArc::source function allowing the user to drop an object in a different thread than the one it was acquired in (#50). This is a breaking change, but in the name of soundness. Therefore it doesn't break any valid behavior.
  • Fix a bug where this crate would not compile properly on wasm64 (#51).

Version 2.7.0

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

Version 2.6.0

  • Add OnceCell. (#27)
  • Support wasm64.

Version 2.5.0

... (truncated)

Commits

You can trigger a rebase of this PR 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels Mar 27, 2024
@dependabot dependabot bot force-pushed the dependabot/cargo/async-lock-3.3 branch from 19e2ad0 to 09c647a Compare April 3, 2024 20:36
@dependabot dependabot bot force-pushed the dependabot/cargo/async-lock-3.3 branch 6 times, most recently from a9dc31b to 658fa53 Compare April 17, 2024 18:18
@dependabot dependabot bot force-pushed the dependabot/cargo/async-lock-3.3 branch 7 times, most recently from 1a95632 to 7b2c921 Compare April 25, 2024 19:08
Updates the requirements on [async-lock](https://github.com/smol-rs/async-lock) to permit the latest version.
- [Release notes](https://github.com/smol-rs/async-lock/releases)
- [Changelog](https://github.com/smol-rs/async-lock/blob/master/CHANGELOG.md)
- [Commits](smol-rs/async-lock@v2.8.0...v3.3.0)

---
updated-dependencies:
- dependency-name: async-lock
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/cargo/async-lock-3.3 branch from 7b2c921 to 13b9edb Compare April 25, 2024 21:48
Copy link
Author

dependabot bot commented on behalf of github Jun 7, 2024

Superseded by #85.

@dependabot dependabot bot closed this Jun 7, 2024
@dependabot dependabot bot deleted the dependabot/cargo/async-lock-3.3 branch June 7, 2024 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file rust Pull requests that update Rust code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants