fix(deps): update rust crate spin to 0.12.0#4
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
ee1f49b to
25ceced
Compare
25ceced to
c418ca5
Compare
577431b to
569ede3
Compare
569ede3 to
846946b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.9.8→0.12.0Release Notes
zesterer/spin (spin)
v0.12.1Fixed
Unsoundness in
RwLock'stry_upgradepath for thelock_apiinterface has beenfixed. Note that this unsoundness only affects you if all of the following apply:
RwLockvia thelock_apiinterface specificallyupgradable_readto create an upgradeable lock guardtry_upgradeon the upgradeable lock guardLazyLock'sSyncimplementation is now less restrictivev0.12.0Changed
Fixed
FairMutexcaused by an undue extension of a reference lifetimeoutside of a critical section. Note that we do not consider this CVE-worthy since
there's no clear path to exploiting this and there's no clear reason for the compiler
to actually generate code that falls afoul of the issue. If you have found an example
of this issue leading to unexpected behaviour in practice, please open an issue.
v0.11.0Added
lock_apimapped read/write guard forRwLockOnce::init_from_refrustc-dep-of-stdfeature, allowingspinto be used as a standard library dependencyChanged
1.71Lazyis nowLazyLockFixed
lock_apifeature name forRawRwLockUpgradeDowngradev0.10.0Added
Mutex::try_lock_weakRwLock::try_write_weakRwLock::try_upgrade_weakChanged
dep:syntax in Cargo.tomlportable_atomicfeature has been renamed toportable-atomic, for consistency.Fixed
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.