chore(deps): update quay.io/hummingbird/go docker tag to v1.26.4 #205
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!205
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/205/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:
1.26.3-builder→1.26.4-builderConfiguration
📅 Schedule: (UTC)
* * * * *)🚦 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.
🔕 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-9mttt is running.
Starting Pipelinerun forgejo-mcp-code-scans-9mttt 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-9mttt -fop1st Pipelines as Code/forgejo-mcp-on-pull-request- has failed.
There was an error creating the PipelineRun: forgejo-mcp-on-pull-request-
cannot use the API on the provider platform to create a in_progress status:
op1st Pipelines as Code/forgejo-mcp-code-scans-9mttt has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
/test
op1st Pipelines as Code/forgejo-mcp-code-scans-cqqlg is running.
Starting Pipelinerun forgejo-mcp-code-scans-cqqlg 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-cqqlg -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-xcgb7 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-xcgb7 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-xcgb7 -fop1st Pipelines as Code/forgejo-mcp-code-scans-cqqlg has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-xcgb7 has successfully validated your commit.
Task Statuses:
fetch-source
commit-title-check
build-and-test
op1st Pipelines as Code/forgejo-mcp-code-scans-j654m is running.
Starting Pipelinerun forgejo-mcp-code-scans-j654m 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-j654m -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-lh59w is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-lh59w 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-lh59w -fop1st Pipelines as Code/forgejo-mcp-code-scans-j654m has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-lh59w has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-b7klx is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-b7klx 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-b7klx -fop1st Pipelines as Code/forgejo-mcp-code-scans-ctwrd is running.
Starting Pipelinerun forgejo-mcp-code-scans-ctwrd 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-ctwrd -fop1st Pipelines as Code/forgejo-mcp-code-scans-ctwrd has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-b7klx has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-4s46r is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-4s46r 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-4s46r -fop1st Pipelines as Code/forgejo-mcp-code-scans-5sjsj is running.
Starting Pipelinerun forgejo-mcp-code-scans-5sjsj 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-5sjsj -fop1st Pipelines as Code/forgejo-mcp-code-scans-5sjsj has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-4s46r has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-sttsm is running.
Starting Pipelinerun forgejo-mcp-code-scans-sttsm 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-sttsm -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-qh7r2 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-qh7r2 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-qh7r2 -fop1st Pipelines as Code/forgejo-mcp-code-scans-sttsm has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-qh7r2 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-mbmpm is running.
Starting Pipelinerun forgejo-mcp-code-scans-mbmpm 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-mbmpm -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-wfwfz is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-wfwfz 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-wfwfz -fop1st Pipelines as Code/forgejo-mcp-code-scans-mbmpm has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-wfwfz has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-fj22h is running.
Starting Pipelinerun forgejo-mcp-code-scans-fj22h 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-fj22h -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-699xh is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-699xh 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-699xh -fop1st Pipelines as Code/forgejo-mcp-code-scans-fj22h has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-699xh has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-9h2qw is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-9h2qw 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-9h2qw -fop1st Pipelines as Code/forgejo-mcp-code-scans-dgb9h is running.
Starting Pipelinerun forgejo-mcp-code-scans-dgb9h 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-dgb9h -fop1st Pipelines as Code/forgejo-mcp-code-scans-dgb9h has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-9h2qw has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-lrlfw is running.
Starting Pipelinerun forgejo-mcp-code-scans-lrlfw 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-lrlfw -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-jdv4d is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-jdv4d 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-jdv4d -fop1st Pipelines as Code/forgejo-mcp-code-scans-lrlfw has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-jdv4d has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check