chore(deps): update quay.io/hummingbird/go:1.26.4-builder docker digest to 1dbf14b #272
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!272
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/272/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:
2c1f6ee→1dbf14bConfiguration
📅 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-s4ggm is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-s4ggm 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-s4ggm -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-s4ggm has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-j7p8z is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-j7p8z 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-j7p8z -fop1st Pipelines as Code/forgejo-mcp-code-scans-g5ktj is running.
Starting Pipelinerun forgejo-mcp-code-scans-g5ktj 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-g5ktj -fop1st Pipelines as Code/forgejo-mcp-code-scans-g5ktj has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-j7p8z has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check