Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 15, 2024

This PR contains the following updates:

Package Type Update Change
volatile dependencies minor =0.2.6 -> =0.6.1

Release Notes

rust-osdev/volatile (volatile)

v0.6.1

Compare Source

v0.6.0

Compare Source

Full Changelog: rust-osdev/volatile@v0.5.4...0.6.0

v0.5.4

Compare Source

Full Changelog: rust-osdev/volatile@v0.5.4...0.6.0

v0.5.3

Compare Source

v0.5.2

Compare Source

  • Add implementations for fmt::Pointer, PartialEq, Eq, PartialOrd, Ord and Hash.
  • Update very_unstable feature to latest nightly
  • Remove Sized requirement for Send and Sync impls on VolatileRef

v0.5.1

Compare Source

  • Fix: Add missing documentation of the map macro

v0.5.0

Compare Source

  • Breaking: New design based on raw pointers
    • The previous reference-based design was unsound because it allowed the compiler to insert spurious reads.
    • The new design features two wrapper types for raw pointers: VolatilePtr and VolatileRef
    • VolatilePtr provides safe read and write access to volatile values. Like raw pointers, it implements Copy and is !Sync.
    • VolatileRef is a pointer type that respects Rust's aliasing rules. It doesn't implement Copy, requires a &mut reference for modification, and implements Sync. It can converted to temporary VolatilePtr instances through the as_ptr/as_mut_ptr methods.
  • We now provide methods for volatile slice operations and a map! macro for struct field projection. These advanced features are gated behind a cargo feature named "unstable".

v0.4.6

Compare Source

  • Fix UB in slice methods when Deref returns different references (#​27)

v0.4.5

Compare Source

  • Remove the const_generics feature flag (#​25)

v0.4.4

Compare Source

  • Replace feature "range_bounds_assert_len" with "slice_range" (#​21)
    • Fixes the unstable feature on the latest nightly.

v0.4.3

Compare Source

  • Add methods to restrict access (#​19)

v0.4.2

Compare Source

  • Change slice::check_range to RangeBounds::assert_len (#​16)
    • Fixes build on latest nightly.

v0.4.1

Compare Source

  • Small documentation and metadata improvements

v0.4.0

Compare Source

  • Breaking: Rewrite crate to operate on reference values (#​13)

v0.3.0

Compare Source

  • Breaking: Remove Debug and Clone derives for WriteOnly (#​12)

v0.2.7

Compare Source

  • Derive Default for Volatile, WriteOnly and ReadOnly (#​10)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/volatile-0.x branch 2 times, most recently from 3121aeb to f445e32 Compare November 15, 2024 08:54
@renovate renovate bot force-pushed the renovate/volatile-0.x branch from f445e32 to ae715e8 Compare January 27, 2025 14:24
@renovate renovate bot force-pushed the renovate/volatile-0.x branch from ae715e8 to e177da4 Compare August 10, 2025 14:15
@renovate renovate bot force-pushed the renovate/volatile-0.x branch from e177da4 to fb1ff34 Compare September 25, 2025 18:29
Copy link
Contributor Author

renovate bot commented Sep 25, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.6.1
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants