Skip to content

chore(deps): update dependency gitea/act_runner to v2 - autoclosed - #688

Closed
renovate[bot] wants to merge 1 commit into
trunkfrom
renovate/gitea-act_runner-2.x
Closed

chore(deps): update dependency gitea/act_runner to v2 - autoclosed#688
renovate[bot] wants to merge 1 commit into
trunkfrom
renovate/gitea-act_runner-2.x

Conversation

@renovate

@renovate renovate Bot commented Jul 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
gitea/act_runner major 0.6.1 → 2.3.0

Release Notes

gitea/act_runner (gitea/act_runner)

v2.3.0

Compare Source

Features

Bug fixes

Dependencies

Full changelog: https://gitea.com/gitea/runner/compare/v2.2.0...v2.3.0

v2.2.0

Compare Source

Features

Bug fixes

Dependencies

Full changelog: https://gitea.com/gitea/runner/compare/v2.1.0...v2.2.0

v2.1.0

Compare Source

Features

Bug fixes

Docs

Dependencies

Full changelog: https://gitea.com/gitea/runner/compare/v2.0.1...v2.1.0

v2.0.1

Compare Source

Bug fixes

Tests & docs

Dependencies

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

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.

v1.0.8

Compare Source

  • fix(cleanup): kill Windows step process tree on cancel to avoid hang (#​1011)

v1.0.7

Compare Source

Changelog

  • fix(container): re-validate cached container id before reuse (#​1003)
  • fix: support multiline secret masking (#​1001)
  • fix: restore global docker config dir and socket env in tests (#​1004)
  • fix: matrix-job data races + outputs, leaner offline test suite (#​994)
  • fix: deliver cancel ack and reap leftover Windows job processes (#​996)
  • fix(reporter): respect configured log level for job log forwarding (#​989)

v1.0.6

Compare Source

Changelog

  • fix(deps): update module github.com/opencontainers/selinux to v1.15.0 (#​990)
  • chore: pin Docker base images to explicit versions (#​992)
  • chore(deps): update actions/setup-node action to v6 (#​991)
  • test: make TestRunEvent integration suite runnable locally (#​987)
  • ci: add PR title linting against Conventional Commits (#​988)
  • fix: clean up job network and container when container start fails (#​986)

v1.0.5

Compare Source

Changelog

  • fix(deps): update module connectrpc.com/connect to v1.20.0 (#​985)
  • update docker cli to v29.5.2 (#​984)
  • feat: add cache.offline_mode to reuse cached actions (#​966)
  • Remove stale Gitea 1.20 compatibility shims (#​978)
  • fix(deps): update module github.com/docker/cli to v29.5.1+incompatible (#​979)
  • fix(deps): update module github.com/go-git/go-git/v5 to v5.19.1 (#​980)

v1.0.4

Compare Source

Changelog

  • Fix token use with schemaless Gitea instance (#​977)
  • Add OCI source and version labels to images (#​975)
  • fix(parse_env_file): support env-file lines larger than 64 KiB (#​974)
  • Fix host cleanup, volume allowlist, cache upload, and action host edge cases (#​970)
  • Remove dead code from act/ (#​971)
  • fix: Return if executors length is zero in ParallelExecutor (#​960)
  • feat: make pseudo-TTY allocation opt-in (#​961)
  • fix(deps): update module github.com/docker/cli to v29.5.0+incompatible (#​969)
  • Simplify kubernetes dind example allowing for default docker config in workflows (#​709)
  • chore(deps): bump retry-go, golangci-lint, govulncheck (#​965)
  • fix(deps): bump docker deps, switch to moby/moby (#​943)
  • fix: respect proxy env vars in runner client (#​962)

v1.0.3

Compare Source

Changelog

  • fix: isolate per-task runner envs (#​959)
  • fix(deps): update module github.com/opencontainers/selinux to v1.14.1 (#​955)
  • fix(deps): update mergo to v1.0.2 (now dario.cat/mergo) (#​954)
  • fix: ensure dbfs_data is cleaned up after task completion (#​952)
  • fix(artifactcache): preserve cache key case to stop redundant uploads (#​947)
  • fix(deps): update module golang.org/x/term to v0.43.0 (#​948)

v1.0.2

Compare Source

Changelog

  • fix: overwrite read-only files when copying action directories (#​942)
  • docs: add apparmor=rootlesskit in security_opt (#​937)
  • fix: serialize action-cache reads to prevent worktree race (#​938)
  • feat: remove emojis from runner logging, add Starting job container group (#​940)

v1.0.1

Compare Source

Changelog

  • dff63b3 fix(deps): update module github.com/go-git/go-git/v5 to v5.19.0 (#​934)
  • a5d9fe9 fix(deps): update module github.com/opencontainers/selinux to v1.14.0 (#​928)
  • d607f3b test: clean up dead/stale fixtures and bump test container images (#​932)
  • 5e59402 fix: re-fetch cached reusable workflow on every run (#​930)
  • dfeb463 chore(deps): update docker docker tag to v29 (#​924)

v1.0.0

Compare Source

This is the first release under the new name gitea-runner. The project was previously published as act_runner and has been renamed end-to-end — including the canonical repository, which now lives at gitea/runner (the old gitea/act_runner URL still redirects). Operators upgrading from act_runner must update wrapper scripts, systemd units, container images, monitoring, and any code importing the Go module.

Breaking changes

The full rename in #​850 changed many user-visible names:

  • Repository: gitea.com/gitea/act_runner → gitea.com/gitea/runner. The old URL redirects, but bookmarks, CI checkouts, and go get paths should be updated.
  • Binary: act_runner → gitea-runner. Wrapper scripts, systemd units, init scripts, and docs referencing act_runner will break.
  • Docker image: gitea/act_runner → gitea/runner (incl. *-dind-rootless variants). Pulls of gitea/act_runner:nightly etc. will return stale images.
  • Go module path: gitea.com/gitea/act_runner → gitea.com/gitea/runner. Anything importing act/... or internal/... packages (notably Gitea itself) must update imports.
  • Release artifact paths: S3 directory act_runner/{{.Version}} → gitea-runner/{{.Version}}, and artifact filenames change accordingly. Existing download URLs break.
  • Prometheus metrics namespace: act_runner_* → gitea_runner_* (e.g. act_runner_jobs_total → gitea_runner_jobs_total). Existing dashboards and alerts must be updated.
  • ldflags version path: gitea.com/gitea/act_runner/internal/pkg/ver.version → gitea.com/gitea/runner/internal/pkg/ver.version. Affects custom builds that stamp the version.
  • Kubernetes example resources: act-runner / act-runner-vol → runner / runner-vol. Users who copied the manifests verbatim will see resource churn on apply.
  • s6 service name: scripts/s6/act_runner/ → scripts/s6/gitea-runner/. Only matters for downstream image overrides.

Unchanged: YAML config field names, env vars (GITEA_*), CLI flags and subcommands, registration file format.

User-facing changes

  • Idle-time workspace janitor (#​870). Stale bind-workdir task workspaces are now cleaned up in the background instead of on the task execution path. Two new config keys: runner.startup_cleanup_age (stale-age threshold, default 24h) and runner.idle_cleanup_interval (cleanup cadence, default 10m). Cleanup is scoped to numeric task directory names only, so operator-managed folders are left alone.
  • Step failure log output now matches GitHub Actions (#​927). The error block printed when a step fails has been realigned with the GitHub Actions format.
  • Host-mode workspace cleanup fixed on Windows (#​883). Host-mode runs now remove the job workspace after the run instead of leaving checkouts behind. On Windows, remaining step process trees are terminated during teardown before workspace deletion to avoid file-lock failures. Cleanup is skipped when bind_workdir is enabled, to avoid conflicting with the runner-level janitor above.

Changelog

  • Align step failure log output with GitHub Actions (#​927)
  • feat: add startup janitor for stale bind-workdir task workspaces (#​870)
  • fix(host): correct host workspace cleanup on Windows (#​883)
  • chore(deps): update crazy-max/ghaction-import-gpg action to v7 (#​923)
  • fix(deps): update module golang.org/x/term to v0.42.0 (#​920)
  • chore(deps): update actions/hello-world-docker-action action to v2 (#​921)
  • ci: Fix triggers (#​882)
  • chore(deps): update dependency @​vercel/ncc to ^0.38.0 (#​881)
  • chore(deps): update dependency @​actions/core to v1.11.1 (#​880)
  • fix(deps): update module github.com/rhysd/actionlint to v1.7.12 (#​873)
  • Rename act_runner to runner (#​850)
  • docs: Update docs (#​872)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)

🚦 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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/gitea-act_runner-2.x branch from 7f2db8c to 91ff04c Compare July 22, 2026 23:37
@renovate
renovate Bot force-pushed the renovate/gitea-act_runner-2.x branch from 91ff04c to 088d92f Compare July 28, 2026 06:52
@renovate renovate Bot changed the title chore(deps): update dependency gitea/act_runner to v2 chore(deps): update dependency gitea/act_runner to v2 - autoclosed Jul 31, 2026
@renovate renovate Bot closed this Jul 31, 2026
@renovate
renovate Bot deleted the renovate/gitea-act_runner-2.x branch July 31, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants