chore(deps): update quay.io/hummingbird/core-runtime:2.42 docker digest to b9bbc03 #259
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!259
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/259/head"
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:
dcd72ea→b9bbc03Configuration
📅 Schedule: (UTC)
* * * * *)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
op1st Pipelines as Code/forgejo-mcp-on-pull-request-khrqs is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-khrqs 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-khrqs -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-khrqs 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-92zsg is running.
Starting Pipelinerun forgejo-mcp-code-scans-92zsg 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-92zsg -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-sczmg is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-sczmg 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-sczmg -fop1st Pipelines as Code/forgejo-mcp-code-scans-92zsg has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-sczmg has failed.
Task Statuses:
fetch-source
commit-title-check
build-and-test
Failure snippet:
task build-and-test has the status "Failed":op1st Pipelines as Code/forgejo-mcp-code-scans-jqvhz is running.
Starting Pipelinerun forgejo-mcp-code-scans-jqvhz 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-jqvhz -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-vglbp is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-vglbp 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-vglbp -fop1st Pipelines as Code/forgejo-mcp-code-scans-jqvhz has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-vglbp 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-vrddp is running.
Starting Pipelinerun forgejo-mcp-code-scans-vrddp 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-vrddp -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-zhdnl is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-zhdnl 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-zhdnl -fop1st Pipelines as Code/forgejo-mcp-code-scans-vrddp has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-zhdnl 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-df6fk is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-df6fk 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-df6fk -fop1st Pipelines as Code/forgejo-mcp-code-scans-gz4sd is running.
Starting Pipelinerun forgejo-mcp-code-scans-gz4sd 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-gz4sd -fop1st Pipelines as Code/forgejo-mcp-code-scans-gz4sd has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-df6fk 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-dlc8z is running.
Starting Pipelinerun forgejo-mcp-code-scans-dlc8z 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-dlc8z -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-9n8xd is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-9n8xd 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-9n8xd -fop1st Pipelines as Code/forgejo-mcp-code-scans-dlc8z has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-9n8xd has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check