chore(deps): update quay.io/hummingbird/go:1.26.4-builder docker digest to 37676d9 #260
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!260
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/260/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:
6e77e0a→37676d9Configuration
📅 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-code-scans-j2sn2 is running.
Starting Pipelinerun forgejo-mcp-code-scans-j2sn2 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-j2sn2 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-v4mnc is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-v4mnc 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-v4mnc -fop1st Pipelines as Code/forgejo-mcp-code-scans-j2sn2 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-v4mnc 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-48bff is running.
Starting Pipelinerun forgejo-mcp-code-scans-48bff 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-48bff -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-lck6b is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-lck6b 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-lck6b -fop1st Pipelines as Code/forgejo-mcp-code-scans-48bff has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-lck6b 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-lck6b 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-cjmcd is running.
Starting Pipelinerun forgejo-mcp-code-scans-cjmcd 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-cjmcd -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-tmwsx is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-tmwsx 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-tmwsx -fop1st Pipelines as Code/forgejo-mcp-code-scans-cjmcd has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-tmwsx 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-t7fz4 is running.
Starting Pipelinerun forgejo-mcp-code-scans-t7fz4 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-t7fz4 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-m4c4f is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-m4c4f 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-m4c4f -fop1st Pipelines as Code/forgejo-mcp-code-scans-t7fz4 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-m4c4f 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-jjvbp is running.
Starting Pipelinerun forgejo-mcp-code-scans-jjvbp 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-jjvbp -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-tr956 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-tr956 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-tr956 -fop1st Pipelines as Code/forgejo-mcp-code-scans-jjvbp has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-tr956 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-sfcpc is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-sfcpc 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-sfcpc -fop1st Pipelines as Code/forgejo-mcp-code-scans-n4nhc is running.
Starting Pipelinerun forgejo-mcp-code-scans-n4nhc 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-n4nhc -fop1st Pipelines as Code/forgejo-mcp-code-scans-n4nhc has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-code-scans-n4nhc has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-sfcpc has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check