Skip to content

chore(deps): update rust crate atomic-write-file to v0.3.1 - #7081

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/atomic-write-file-0.3.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/atomic-write-file-0.3.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
atomic-write-file dependencies patch 0.3.0 → 0.3.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

andreacorbellini/rust-atomic-write-file (atomic-write-file)

v0.3.1

Compare Source

Unix changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 requested a review from a team as a code owner August 31, 2026 02:19
@renovate
renovate Bot enabled auto-merge (squash) August 31, 2026 02:19
@renovate

renovate Bot commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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
    Updating crates.io index
error: failed to select a version for `rand`.
    ... required by package `atomic-write-file v0.3.1`
    ... which satisfies dependency `atomic-write-file = "^0.3"` of package `buzz-voice v0.1.0 (/tmp/renovate/repos/github/block/buzz/crates/buzz-voice)`
versions that meet the requirements `^0.10.2` are: 0.10.3, 0.10.2

all possible versions conflict with previously selected packages

  previously selected package `rand v0.10.1`
    ... which satisfies dependency `rand = "^0.10"` (locked to 0.10.1) of package `buzz-backend-kubernetes v0.1.0 (/tmp/renovate/repos/github/block/buzz/crates/buzz-backend-kubernetes)`

failed to select a version for `rand` which could resolve this conflict

@github-actions

github-actions Bot commented Aug 31, 2026 •

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 0ee609379004a894e99b449885c37a044f41919e...0a9751df5af602ddab3436f5a2819cce701d2203.
A new review must complete for this exact range. When manual authorization
is required, a user with write access must comment exactly
@buzz-security-review 0a9751df5af602ddab3436f5a2819cce701d2203 to authorize a new review.
Any previous review applies only to its recorded range.

@renovate
renovate Bot force-pushed the renovate/atomic-write-file-0.3.x-lockfile branch 3 times, most recently from 3e1e147 to 0786fb0 Compare September 8, 2026 14:37
@renovate
renovate Bot force-pushed the renovate/atomic-write-file-0.3.x-lockfile branch 2 times, most recently from 5bd37a5 to 585dd87 Compare September 16, 2026 11:57
@renovate
renovate Bot force-pushed the renovate/atomic-write-file-0.3.x-lockfile branch from 585dd87 to de86299 Compare September 24, 2026 13:35
@renovate
renovate Bot force-pushed the renovate/atomic-write-file-0.3.x-lockfile branch from de86299 to 0a9751d Compare September 30, 2026 16:28

This branch has not been deployed

No deployments
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