Version metadata not working in v5.8.0

[Meldiron]

Contributing guidelines

• I've read the contributing guidelines and wholeheartedly agree

I've found a bug, and:

• The documentation does not mention anything about my problem
• There are no open or closed issues that are related to my problem

Description

Image cannot be pushed, originating from metadata issue of extracting version:

##[debug]manifest:org.opencontainers.image.version='

This stopped working recently, so my best guess is issue in most recent release of 5.8.0 instead of 5.7.0, because our job used v5.

The problem was solved for now by downgrading to 5.7.0 version.

Expected behaviour

Existing v5 jobs remain working with new minor version

Actual behaviour

Job fails due to version extraction issue

Repository URL

https://github.com/appwrite/console/

Workflow run URL

https://github.com/appwrite/console/actions/runs/16882183410/job/47827714696

YAML workflow

https://github.com/appwrite/console/blob/main/.github/workflows/publish.yml

Workflow logs

No response

BuildKit logs

  {
    "target": {
      "docker-metadata-action": {
        "annotations": [
          "manifest:org.opencontainers.image.created=2025-08-11T15:15:31.165Z",
          "manifest:org.opencontainers.image.description=The Console that makes Appwrite tick from the browser  🖥",
          "manifest:org.opencontainers.image.licenses=BSD-3-Clause",
          "manifest:org.opencontainers.image.revision=29e85017ed2bf87a866af6a3263927d93d6fa296",
          "manifest:org.opencontainers.image.source=https://github.com/appwrite/console",
          "manifest:org.opencontainers.image.title=console",
          "manifest:org.opencontainers.image.url=https://github.com/appwrite/console",
          "manifest:org.opencontainers.image.version="
        ]
      }
    }
  }

Additional info

For refference, following PR fixed it temporarly: appwrite/console#2209

With a working job now: https://github.com/appwrite/console/actions/runs/16884720878/job/47829359004

[crazy-max]

Thanks for reporting, we are taking a look.

[crazy-max]

Seems GitHub ref is empty in 5.8.0 https://github.com/appwrite/console/actions/runs/16882183410/job/47827714696#step:6:31

  eventName: release
  sha: 29e85017ed2bf87a866af6a3263927d93d6fa296
  ref: 
  workflow: Publish
  action: meta
  actor: Meldiron
  runNumber: 337
  runId: 16882183410
  commitDate: Mon Aug 11 2025 13:52:31 GMT+0000 (Coordinated Universal Time)

But set in 5.7.0: https://github.com/appwrite/console/actions/runs/16884720878/job/47829359004#step:6:14

  eventName: release
  sha: dd61875d43731e6cc9dfb6486bd213a00a570784
  ref: refs/tags/6.1.30
  workflow: Publish
  action: meta
  actor: Meldiron
  runNumber: 338
  runId: 16884720878
  commitDate: Mon Aug 11 2025 15:31:15 GMT+0000 (Coordinated Universal Time)

Might be related to dependency update

[crazy-max]

But set in 5.7.0: https://github.com/appwrite/console/actions/runs/16884720878/job/47829359004#step:6:14

  eventName: release
  sha: dd61875d43731e6cc9dfb6486bd213a00a570784
  ref: refs/tags/6.1.30
  workflow: Publish
  action: meta
  actor: Meldiron
  runNumber: 338
  runId: 16884720878
  commitDate: Mon Aug 11 2025 15:31:15 GMT+0000 (Coordinated Universal Time)

...

With a working job now: https://github.com/appwrite/console/actions/runs/16884720878/job/47829359004

@Meldiron Actually this one is using @v5 5.8.0 not 5.7.0: https://github.com/appwrite/console/actions/runs/16884720878/job/47829359004#step:1:61

Download immutable action package 'docker/metadata-action@v5'
  Version: 5.8.0
  Digest: sha256:ac0510c1bcaf77229cc55556e65fb04fbb39e28bef6bafe9d6726d525aab1831
  Source commit SHA: c1e51972afc2121e065aed6d45c65596fe445f3f

https://github.com/appwrite/console/actions/runs/16884720878/workflow#L24

[crazy-max]

I cannot repro on my side for release or push tags events:

name: metadata

on:
  release:

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      -
        name: Event
        run: cat $GITHUB_EVENT_PATH
      -
        name: Docker meta
        uses: docker/metadata-action@master
        with:
          images: |
            localhost:5000/name/app
            ghcr.io/name/app
          tags: |
            type=schedule
            type=ref,event=branch
            type=ref,event=tag
            type=ref,event=pr
            type=semver,pattern={{major}}.{{minor}}.{{patch}}
            type=semver,pattern={{major}}.{{minor}}
            type=semver,pattern={{major}}
            type=edge
            type=sha
      -
        name: Dump context
        uses: crazy-max/ghaction-dump-context@v2

I have the expected ref and org.opencontainers.image.version set accordingly:

I wonder if this might have been something flaky on GitHub side.

@Meldiron Can you check again on your side? Thanks.

[polarathene]

The original reporter of the issue doesn't seem to have a problem with their publish workflow (public action logs show full version now). Presumably there was an issue in deriving the value so it used the empty fallback:

metadata-action/src/meta.ts

Line 546 in ed95091

`org.opencontainers.image.version=${this.version.main || ''}`,

When the fallback value is used (empty string), the label/annotation is still exported when perhaps it should have been omitted/filtered out? Other than that this can probably be closed.

---

UPDATE: This caveat was covered in the README priority section, which I guess depends on tag types used rather than just the semver scenario 😓 so not sure if there's any improvements docs wise for being aware of that (there was a misunderstanding in the past regarding priority, but this could be better addressed by documenting default label behaviour).

The OCI spec for annotations notes the version should represent the semver version in full.

I'm providing the semver value via a workflow call input and giving it to a tag config as value={ inputs.version }, and noticing that the version in label/annotation set is only the major version 🤔

EDIT: I identified that my related issue is from how the this.version.main is initialized:

metadata-action/src/meta.ts

Lines 357 to 371 in ed95091

	private static setVersion(version: Version, val: string, latest: boolean): Version {
	if (val.length == 0) {
	return version;
	}
	val = Meta.sanitizeTag(val);
	if (version.main == undefined) {
	version.main = val;
	} else if (val !== version.main) {
	version.partial.push(val);
	}
	if (version.latest == undefined) {
	version.latest = latest;
	}
	return version;
	}

My problem was due to the first semver pattern using the major version only, which triggered the first call to that setVersion() function.

name: 'Build and Publish the container image'

on:
  workflow_dispatch:
    inputs:
      version:
        description: 'Version to build (e.g., 1.42.0)'
        required: true
        type: string

jobs:
  container:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write
    steps:
      - name: Prepare image metadata
        id: metadata
        uses: docker/metadata-action@v5
        with:
          images: |
            ghcr.io/${{ github.repository }}
          tags: |
            type=semver,pattern={{major}},value=${{ inputs.version }}
            type=semver,pattern={{major}}.{{minor}},value=${{ inputs.version }}
            type=semver,pattern={{major}}.{{minor}}.{{patch}},value=${{ inputs.version }}

      # ...