chore(deps): lock file maintenance #251
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!251
Loading…
Reference in a new issue
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?
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)* * * * *)🚦 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate.
op1st Pipelines as Code/forgejo-mcp-on-pull-request-2ffkj is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-2ffkj in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-2ffkj -fop1st Pipelines as Code/forgejo-mcp-code-scans-czssc is running.
Starting Pipelinerun forgejo-mcp-code-scans-czssc in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-czssc -fop1st Pipelines as Code/forgejo-mcp-code-scans-czssc has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-2ffkj has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-xcwzp is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-xcwzp in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-xcwzp -fop1st Pipelines as Code/forgejo-mcp-code-scans-xrwfb is running.
Starting Pipelinerun forgejo-mcp-code-scans-xrwfb in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-xrwfb -fop1st Pipelines as Code/forgejo-mcp-code-scans-xrwfb has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-xcwzp has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-rz6tm is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-rz6tm in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-rz6tm -fop1st Pipelines as Code/forgejo-mcp-code-scans-hkm6r is running.
Starting Pipelinerun forgejo-mcp-code-scans-hkm6r in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-hkm6r -fop1st Pipelines as Code/forgejo-mcp-code-scans-hkm6r has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-rz6tm has failed.
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "Failed":op1st Pipelines as Code/forgejo-mcp-on-pull-request-pf8hp is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-pf8hp in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-pf8hp -fop1st Pipelines as Code/forgejo-mcp-code-scans-98z8c is running.
Starting Pipelinerun forgejo-mcp-code-scans-98z8c in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-98z8c -fop1st Pipelines as Code/forgejo-mcp-code-scans-98z8c has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-pf8hp has failed.
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "Failed":op1st Pipelines as Code/forgejo-mcp-on-pull-request-vccql is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-vccql in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-vccql -fop1st Pipelines as Code/forgejo-mcp-code-scans- has failed.
There was an error creating the PipelineRun: forgejo-mcp-code-scans-
cannot use the API on the provider platform to create a in_progress status:
op1st Pipelines as Code/forgejo-mcp-on-pull-request-vccql has failed.
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "Failed":op1st Pipelines as Code/forgejo-mcp-code-scans-wnj7d is running.
Starting Pipelinerun forgejo-mcp-code-scans-wnj7d in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-wnj7d -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-sqkkd is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-sqkkd in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-sqkkd -fop1st Pipelines as Code/forgejo-mcp-code-scans-wnj7d has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-sqkkd has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-6xbr7 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-6xbr7 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-6xbr7 -fop1st Pipelines as Code/forgejo-mcp-code-scans-8kk2g is running.
Starting Pipelinerun forgejo-mcp-code-scans-8kk2g in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-8kk2g -fop1st Pipelines as Code/forgejo-mcp-code-scans-8kk2g has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-6xbr7 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-n9lht is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-n9lht in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-n9lht -fop1st Pipelines as Code/forgejo-mcp-code-scans-4vk8j is running.
Starting Pipelinerun forgejo-mcp-code-scans-4vk8j in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-4vk8j -fop1st Pipelines as Code/forgejo-mcp-code-scans-4vk8j has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-n9lht has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-n9lht has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check