goern/forgejo-mcp
9
120
Fork
You've already forked forgejo-mcp
30

chore(deps): update registry.access.redhat.com/hi/go:latest-builder docker digest to e1d04a2 #346

Merged
b4mad-renovate merged 1 commit from renovate/registry.access.redhat.com-hi-go-latest-builder into main 2026年07月10日 18:17:10 +02:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/hi/go final digest 050af63e1d04a2
registry.access.redhat.com/hi/go stage digest 050af63e1d04a2

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Every minute (* * * * *)

🚦 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | registry.access.redhat.com/hi/go | final | digest | `050af63` → `e1d04a2` | | registry.access.redhat.com/hi/go | stage | digest | `050af63` → `e1d04a2` | --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - Every minute (`* * * * *`) 🚦 **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 these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNjguNiIsInVwZGF0ZWRJblZlciI6IjQzLjE2OC42IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
chore(deps): update registry.access.redhat.com/hi/go:latest-builder docker digest to e1d04a2
All checks were successful
op1st Pipelines as Code / forgejo-mcp-code-scans Success
op1st Pipelines as Code / forgejo-mcp-on-pull-request Success
57a4e20fde
b4mad-renovate scheduled this pull request to auto merge when all checks succeed 2026年07月10日 18:13:14 +02:00
Collaborator
Copy link

op1st Pipelines as Code/forgejo-mcp-code-scans-2zf27 is running.

Starting Pipelinerun forgejo-mcp-code-scans-2zf27 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-2zf27 -f

op1st Pipelines as Code/forgejo-mcp-code-scans-2zf27 is running. Starting Pipelinerun <b>[forgejo-mcp-code-scans-2zf27](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-code-scans-2zf27)</b> in namespace <b>op1st-pipelines</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-code-scans-2zf27) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-2zf27 -f</code>
Collaborator
Copy link

op1st Pipelines as Code/forgejo-mcp-on-pull-request-hqnkf is running.

Starting Pipelinerun forgejo-mcp-on-pull-request-hqnkf 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-hqnkf -f

op1st Pipelines as Code/forgejo-mcp-on-pull-request-hqnkf is running. Starting Pipelinerun <b>[forgejo-mcp-on-pull-request-hqnkf](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-on-pull-request-hqnkf)</b> in namespace <b>op1st-pipelines</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-on-pull-request-hqnkf) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-hqnkf -f</code>
Collaborator
Copy link

op1st Pipelines as Code/forgejo-mcp-code-scans-2zf27 has successfully validated your commit.


Task Statuses:

StatusDurationName
Succeeded 15 seconds

fetch-source

Succeeded 11 seconds

gitleaks-version

Succeeded 21 seconds

gitleaks

op1st Pipelines as Code/forgejo-mcp-code-scans-2zf27 has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">op1st-pipelines</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-code-scans-2zf27">forgejo-mcp-code-scans-2zf27</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>15 seconds</td><td> [fetch-source](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-code-scans-2zf27/logs/fetch-source) </td></tr> <tr> <td>Succeeded</td> <td>11 seconds</td><td> [gitleaks-version](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-code-scans-2zf27/logs/gitleaks-version) </td></tr> <tr> <td>Succeeded</td> <td>21 seconds</td><td> [gitleaks](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-code-scans-2zf27/logs/gitleaks) </td></tr> </table>
Collaborator
Copy link

op1st Pipelines as Code/forgejo-mcp-on-pull-request-hqnkf has successfully validated your commit.


Task Statuses:

StatusDurationName
Succeeded 19 seconds

fetch-source

Succeeded 3 minutes

build-and-test

Succeeded 24 seconds

commit-title-check

op1st Pipelines as Code/forgejo-mcp-on-pull-request-hqnkf has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">op1st-pipelines</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-on-pull-request-hqnkf">forgejo-mcp-on-pull-request-hqnkf</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>19 seconds</td><td> [fetch-source](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-on-pull-request-hqnkf/logs/fetch-source) </td></tr> <tr> <td>Succeeded</td> <td>3 minutes</td><td> [build-and-test](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-on-pull-request-hqnkf/logs/build-and-test) </td></tr> <tr> <td>Succeeded</td> <td>24 seconds</td><td> [commit-title-check](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/forgejo-mcp-on-pull-request-hqnkf/logs/commit-title-check) </td></tr> </table>
b4mad-renovate deleted branch renovate/registry.access.redhat.com-hi-go-latest-builder 2026年07月10日 18:17:11 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
hermes-attempted
Hermes attempted but produced no changes
hermes-needs-clarification
Quality gate flagged, needs human input
hermes-ready
Ready for hermes to process
hermes-review
Hermes PR awaiting review
hermes-wip
Hermes is working on this
human-required
Hermes gave up after 3 attempts
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/OpenSpec
OpenSpec change proposal / spec-driven work
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
RFC - Request For Comments
Request For Comments — design/spec open for feedback before implementation
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
goern/forgejo-mcp!346
Reference in a new issue
goern/forgejo-mcp
No description provided.
Delete branch "renovate/registry.access.redhat.com-hi-go-latest-builder"

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?