james/outrun
1
0
Fork 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity

chore(deps): lock file maintenance #217

Open
renovate wants to merge 1 commit from renovate/lock-file-maintenance into main
pull from: renovate/lock-file-maintenance
merge into: james:main
Conversation 1 Commits 1 Files changed 1 +25 -16
renovate commented 2024-07-27 17:22:32 +12:00
Collaborator
Copy link

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 - "" in timezone Pacific/Auckland, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

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 - "" in timezone Pacific/Auckland, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC44LjEiLCJ1cGRhdGVkSW5WZXIiOiIzOC4zNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->
james was assigned by renovate 2024-07-27 17:22:34 +12:00
renovate commented 2024-08-09 03:17:07 +12:00
Author
Collaborator
Copy link

⚠️ 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path outrun-common/Cargo.toml
error: current package believes it's in a workspace when it's not:
current:   /drone/src/cache/repos/gitea/james/outrun/outrun-common/Cargo.toml
workspace: /drone/src/cache/repos/gitea/james/outrun/Cargo.toml

this may be fixable by adding `outrun-common` to the `workspace.members` array of the manifest located at: /drone/src/cache/repos/gitea/james/outrun/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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path outrun/Cargo.toml
error: current package believes it's in a workspace when it's not:
current:   /drone/src/cache/repos/gitea/james/outrun/outrun/Cargo.toml
workspace: /drone/src/cache/repos/gitea/james/outrun/Cargo.toml

this may be fixable by adding `outrun` to the `workspace.members` array of the manifest located at: /drone/src/cache/repos/gitea/james/outrun/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.
### ⚠️ 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: Cargo.lock ``` Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path outrun-common/Cargo.toml error: current package believes it's in a workspace when it's not: current: /drone/src/cache/repos/gitea/james/outrun/outrun-common/Cargo.toml workspace: /drone/src/cache/repos/gitea/james/outrun/Cargo.toml this may be fixable by adding `outrun-common` to the `workspace.members` array of the manifest located at: /drone/src/cache/repos/gitea/james/outrun/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: Cargo.lock ``` Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path outrun/Cargo.toml error: current package believes it's in a workspace when it's not: current: /drone/src/cache/repos/gitea/james/outrun/outrun/Cargo.toml workspace: /drone/src/cache/repos/gitea/james/outrun/Cargo.toml this may be fixable by adding `outrun` to the `workspace.members` array of the manifest located at: /drone/src/cache/repos/gitea/james/outrun/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. ```
renovate added 1 commit 2024-08-09 03:17:10 +12:00
chore(deps): lock file maintenance
Some checks failed
renovate/artifacts Artifact file update failure
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/pr Build is passing
Details
01abaaa203
renovate force-pushed renovate/lock-file-maintenance from 01abaaa203 to 24863fc873 2024-09-06 06:08:15 +12:00 Compare
renovate force-pushed renovate/lock-file-maintenance from 24863fc873 to c2b7f041c8 2024-09-06 07:07:20 +12:00 Compare
Some checks failed
renovate/artifacts Artifact file update failure
continuous-integration/drone/push Build is passing
Required
Details
continuous-integration/drone/pr Build is passing
Required
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/lock-file-maintenance:renovate/lock-file-maintenance
git checkout renovate/lock-file-maintenance
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
james
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: james/outrun#217
No description provided.
Delete branch "renovate/lock-file-maintenance"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?