Agent reports incorrect version to server

[DHandspikerWade]

Component

agent

Describe the bug

While running the agent via the woodpeckerci/woodpecker-agent:v3.11.0 container image, the agent reports it's version as "next-7058dbcc96".

Steps to reproduce

1. Setup both the server and agent using the container image tagged with v3.11.0
2. Wait for the initialization
3. Check the agent's version either by reading its logs or navigating to /admin/agents

Expected behavior

I would expect the agent to report with the stable version number.

System Info

{"source":"https://github.com/woodpecker-ci/woodpecker","version":"3.11.0"}

Agent manifest:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  labels:
    app.kubernetes.io/component: agent
    app.kubernetes.io/name: woodpecker
    app.kubernetes.io/version: 3.11.0
  name: woodpecker-agent
  namespace: woodpecker
spec:
  persistentVolumeClaimRetentionPolicy:
    whenDeleted: Retain
    whenScaled: Retain
  podManagementPolicy: OrderedReady
  replicas: 1
  revisionHistoryLimit: 2
  selector:
    matchLabels:
      app.kubernetes.io/component: agent
      app.kubernetes.io/name: woodpecker
  serviceName: woodpecker-agent-headless
  template:
    metadata:
      labels:
        app.kubernetes.io/component: agent
        app.kubernetes.io/name: woodpecker
        app.kubernetes.io/version: 3.11.0
      name: woodpecker-agent
      namespace: woodpecker
    spec:
      containers:
      - env: [ REDACTED ]
        image: woodpeckerci/woodpecker-agent:v3.11.0
        imagePullPolicy: IfNotPresent
        name: agent
        ports:
        - containerPort: 3000
          name: http
          protocol: TCP
        resources:
          requests:
            cpu: 100m
            memory: 128Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /etc/woodpecker
          name: agent-config
      dnsPolicy: ClusterFirst
      priorityClassName: realtime
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: ci-agent
      serviceAccountName: ci-agent
      terminationGracePeriodSeconds: 30
      volumes:
      - name: agent-config
        persistentVolumeClaim:
          claimName: woodpecker-agent-pvc

Additional context

Agent logs:

{"level":"info","time":"2025-10-24T21:35:25Z","message":"log level: info"}
{"level":"info","time":"2025-10-24T21:35:25Z","message":"starting Woodpecker agent with version 'next-7058dbcc96' and backend 'kubernetes' using platform 'linux/amd64' running up to 2 pipelines in parallel"}

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/versions]