chore(deps): lock file maintenance #295
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
approved
area:client-host
area:item-interaction
area:meta-tooling
area:operator-dev-loop
area:repository-hygiene
area:typescript-sdk
area:website
blocked
bug
castra:bot-active
castra:human
change
checker:tobi
close-suggested
code
copilot-conflict
deferred
dependencies
docs-ok
enhancement
fast-track
groom:close-suggested
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human
human-required
intake
merge
merge-conflict
needs-scope
no-concept-doc
no-demo
plan-approved
plan-needs-revision
portfolio:infrastructure
portfolio:mixed
portfolio:product
portfolio:unknown
prioritize
prioritized
priority:high
priority:low
priority:medium
propose
ready
retro
retro-proposal
review
stage:backlog
stage:blocked
stage:code
stage:done
stage:intake
stage:merge
stage:propose
stage:review
stage:waiting
status:waiting
tracker
triage
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!295
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-code-scans-9ql9t is running.
Starting Pipelinerun forgejo-mcp-code-scans-9ql9t 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-9ql9t -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-rc7z7 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-rc7z7 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-rc7z7 -fop1st Pipelines as Code/forgejo-mcp-code-scans-9ql9t has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-rc7z7 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-9vqm2 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-9vqm2 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-9vqm2 -fop1st Pipelines as Code/forgejo-mcp-code-scans-5p6bz is running.
Starting Pipelinerun forgejo-mcp-code-scans-5p6bz 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-5p6bz -fop1st Pipelines as Code/forgejo-mcp-code-scans-5p6bz has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-9vqm2 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-zt6jw is running.
Starting Pipelinerun forgejo-mcp-code-scans-zt6jw 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-zt6jw -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-vntq7 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-vntq7 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-vntq7 -fop1st Pipelines as Code/forgejo-mcp-code-scans-zt6jw has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-vntq7 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-6bmmn is running.
Starting Pipelinerun forgejo-mcp-code-scans-6bmmn 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-6bmmn -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-z7hvr is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-z7hvr 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-z7hvr -fop1st Pipelines as Code/forgejo-mcp-code-scans-6bmmn has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-z7hvr has successfully validated your commit.
Task Statuses:
fetch-source
commit-title-check
build-and-test
op1st Pipelines as Code/forgejo-mcp-code-scans-vzsp5 is running.
Starting Pipelinerun forgejo-mcp-code-scans-vzsp5 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-vzsp5 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-78s8t is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-78s8t 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-78s8t -fop1st Pipelines as Code/forgejo-mcp-code-scans-vzsp5 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-78s8t has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-t5rbs is running.
Starting Pipelinerun forgejo-mcp-code-scans-t5rbs 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-t5rbs -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-lfq7j is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-lfq7j 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-lfq7j -fop1st Pipelines as Code/forgejo-mcp-code-scans-t5rbs has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-lfq7j has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-8dxf5 is running.
Starting Pipelinerun forgejo-mcp-code-scans-8dxf5 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-8dxf5 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-5222k is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-5222k 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-5222k -fop1st Pipelines as Code/forgejo-mcp-code-scans-8dxf5 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-5222k has successfully validated your commit.
Task Statuses:
fetch-source
commit-title-check
build-and-test
op1st Pipelines as Code/forgejo-mcp-on-pull-request-5222k has successfully validated your commit.
Task Statuses:
fetch-source
commit-title-check
build-and-test