Homelab/Docker-Gitea
3
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Update gitea/runner Docker tag to v2 #39

Merged
Akumatic merged 1 commits from renovate/gitea-runner-2.x into main 2026-07-02 11:39:20 +00:00
Conversation 0 Commits 1 Files Changed 1
+1 -1
renovate-bot commented 2026-06-30 16:01:54 +00:00
Member
Copy Link
Copy Source

This PR contains the following updates:

Package Update Change
gitea/runner major 1.0.8 → 2.0.0

Release Notes

gitea/runner (gitea/runner)

v2.0.0

Compare Source

⚠️ Breaking changes

DOCKER_USERNAME / DOCKER_PASSWORD are no longer used implicitly for image pulls

See https://gitea.com/gitea/runner/pulls/1007

The runner previously treated secrets named DOCKER_USERNAME and DOCKER_PASSWORD as implicit Docker pull credentials, attaching them to every job- and step-container image pull unconditionally. Since these credentials carry no registry information, they were even sent to Docker Hub when pulling public images, causing those pulls to fail with authentication errors. This behavior has been removed.

Workflows or runner setups that relied on DOCKER_USERNAME / DOCKER_PASSWORD being implicitly used for Docker image pulls must migrate to an explicit authentication mechanism:

  • For private job container images, use container.credentials:
jobs:
  build:
    container:
      image: registry.example.com/image:tag
      credentials:
        username: ${{ secrets.REGISTRY_USERNAME }}
        password: ${{ secrets.REGISTRY_PASSWORD }}
  • For private service container images, use service credentials.
  • For private uses: docker://... or private Docker actions, configure Docker authentication in the runner environment before the job starts (e.g. run docker login on the runner host).

DOCKER_USERNAME and DOCKER_PASSWORD can still be used as ordinary workflow secrets, for example with docker/login-action before pushing images.

Features

Bug fixes

Build & docs

Dependencies

Full changelog: https://gitea.com/gitea/runner/compare/v1.0.8...v2.0.0

🤖 Release notes compiled by Opus 4.8.

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update 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 | Update | Change | |---|---|---| | [gitea/runner](https://gitea.com/gitea/runner) | major | `1.0.8` → `2.0.0` | --- ### Release Notes <details> <summary>gitea/runner (gitea/runner)</summary> ### [`v2.0.0`](https://gitea.com/gitea/runner/releases/tag/v2.0.0) [Compare Source](https://gitea.com/gitea/runner/compare/v1.0.8...v2.0.0) #### ⚠️ Breaking changes ##### `DOCKER_USERNAME` / `DOCKER_PASSWORD` are no longer used implicitly for image pulls See <https://gitea.com/gitea/runner/pulls/1007> The runner previously treated secrets named `DOCKER_USERNAME` and `DOCKER_PASSWORD` as implicit Docker pull credentials, attaching them to every job- and step-container image pull unconditionally. Since these credentials carry no registry information, they were even sent to Docker Hub when pulling public images, causing those pulls to fail with authentication errors. This behavior has been removed. Workflows or runner setups that relied on `DOCKER_USERNAME` / `DOCKER_PASSWORD` being implicitly used for Docker image pulls must migrate to an explicit authentication mechanism: - For private **job container** images, use `container.credentials`: ```yaml jobs: build: container: image: registry.example.com/image:tag credentials: username: ${{ secrets.REGISTRY_USERNAME }} password: ${{ secrets.REGISTRY_PASSWORD }} ``` - For private **service container** images, use service `credentials`. - For private `uses: docker://...` or private Docker actions, configure Docker authentication in the runner environment before the job starts (e.g. run `docker login` on the runner host). `DOCKER_USERNAME` and `DOCKER_PASSWORD` can still be used as ordinary workflow secrets, for example with `docker/login-action` before pushing images. #### Features - Shallow clone action repositories — <https://gitea.com/gitea/runner/pulls/1053> - Enable `jobs.<job_id>.timeout-minutes` and `jobs.<job_id>.continue-on-error` — <https://gitea.com/gitea/runner/pulls/1032> - Add optional `runner.post_task_script` hook after task cleanup — <https://gitea.com/gitea/runner/pulls/1026> - Support `ssh://` action URLs — <https://gitea.com/gitea/runner/pulls/1035> - IPv6 options for network container creation — <https://gitea.com/gitea/runner/pulls/1029> - Complete runner-side cancellation handling — <https://gitea.com/gitea/runner/pulls/1016> - Upload job summary when supported — <https://gitea.com/gitea/runner/pulls/917> #### Bug fixes - Composite nested `uses` clone token — <https://gitea.com/gitea/runner/pulls/1041> - Namespace local docker action image tags per repository — <https://gitea.com/gitea/runner/pulls/1051> - Run `always()`/`cancelled()` and post steps correctly on cancellation — <https://gitea.com/gitea/runner/pulls/1043> - Guard `SetJobError` against missing job-error container — <https://gitea.com/gitea/runner/pulls/1050> - Interpolate job `container.volume` — <https://gitea.com/gitea/runner/pulls/1036> - Kill Unix step process group on cancel to avoid hang — <https://gitea.com/gitea/runner/pulls/1025> - Prevent loss of step log output at end of step — <https://gitea.com/gitea/runner/pulls/1028> - Bound host-environment cleanup and reclaim leaked scratch dirs — <https://gitea.com/gitea/runner/pulls/1024> - Do not update cached actions with stale origin URL — <https://gitea.com/gitea/runner/pulls/1014> #### Build & docs - Cover Windows Go files in build — <https://gitea.com/gitea/runner/pulls/1052> - Improve cache documentation — <https://gitea.com/gitea/runner/pulls/1034> - Update docker-images docs — <https://gitea.com/gitea/runner/pulls/1020> #### Dependencies - Update `github.com/moby/moby/client` to v0.5.0 — <https://gitea.com/gitea/runner/pulls/1049> - Update `github.com/docker/cli` to v29.6.0 — <https://gitea.com/gitea/runner/pulls/1045> - Update docker docker tag to v29.6.0 — <https://gitea.com/gitea/runner/pulls/1044> - Update `actions/checkout` action to v7 — <https://gitea.com/gitea/runner/pulls/1042> - Update `go.etcd.io/bbolt` to v1.5.0 — <https://gitea.com/gitea/runner/pulls/1040> - Update `golang.org/x/term` to v0.44.0 — <https://gitea.com/gitea/runner/pulls/1031> - Update alpine docker tag to v3.24 — <https://gitea.com/gitea/runner/pulls/1030> - Update `golang.org/x/crypto` to v0.52.0 — <https://gitea.com/gitea/runner/pulls/1027> - Update docker docker tag to v29.5.3 — <https://gitea.com/gitea/runner/pulls/1021> - Update `golang.org/x/sys` to v0.46.0 — <https://gitea.com/gitea/runner/pulls/1019> - Update `github.com/docker/cli` to v29.5.3 — <https://gitea.com/gitea/runner/pulls/1018> - Update `github.com/opencontainers/selinux` to v1.15.1 — <https://gitea.com/gitea/runner/pulls/1017> - Update `golang.org/x/sys` to v0.45.0 — <https://gitea.com/gitea/runner/pulls/1012> - Update `code.gitea.io/actions-proto-go` to v0.5.0 — <https://gitea.com/gitea/runner/pulls/1009> **Full changelog**: <https://gitea.com/gitea/runner/compare/v1.0.8...v2.0.0> 🤖 Release notes compiled by Opus 4.8. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update 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:eyJjcmVhdGVkSW5WZXIiOiI0My4yNDkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI0OS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate-bot added 1 commit 2026-06-30 16:01:54 +00:00
Update gitea/runner Docker tag to v2 f58760c552
Akumatic merged commit f58760c552 into main 2026-07-02 11:39:20 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
Akumatic (Akumatic) Portainer-Bot renovate-bot (Renovate)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Homelab/Docker-Gitea#39