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

Lock file maintenance #36

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 8, 2025

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


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 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.

Copy link
Author

renovate bot commented Jan 8, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts 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: library/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path library/rustc-std-workspace-alloc/Cargo.toml
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/Kobzol/rust/library/rustc-std-workspace-alloc/Cargo.toml
workspace: /tmp/renovate/repos/github/Kobzol/rust/library/Cargo.toml

this may be fixable by adding `rustc-std-workspace-alloc` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/Kobzol/rust/library/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.

File name: library/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path library/rustc-std-workspace-core/Cargo.toml
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/Kobzol/rust/library/rustc-std-workspace-core/Cargo.toml
workspace: /tmp/renovate/repos/github/Kobzol/rust/library/Cargo.toml

this may be fixable by adding `rustc-std-workspace-core` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/Kobzol/rust/library/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.

File name: library/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path library/rustc-std-workspace-std/Cargo.toml
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/Kobzol/rust/library/rustc-std-workspace-std/Cargo.toml
workspace: /tmp/renovate/repos/github/Kobzol/rust/library/Cargo.toml

this may be fixable by adding `rustc-std-workspace-std` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/Kobzol/rust/library/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.

Copy link
Author

renovate bot commented Jan 8, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant