[alexadereyko]

Brief

Let staging-pull find stagings by the annotations of their packages, through staging-check, and download the packages it resolves.

Overview

Stagings are no longer tagged by commit, so staging-pull asks for them the way staging-check does: each entry is resolved by staging-check, and the packages it answers with, path@digest, are downloaded into the artifact.

[
  {
    "artifact": "core-ubuntu-22.04-x86_64-ninja-gcc-release",
    "packages": [
      {
        "path": "ghcr.io/openDAQ/dev/staging/opendaq",
        "annotations": {
          "org.opencontainers.image.revision": "<core commit>",
          "com.opendaq.custom.platform": "linux",
          "com.opendaq.settings.arch": "x86_64"
        }
      }
    ]
  }
]

staging-check comes from the same version as the workflow: the job checks out job.workflow_repository at job.workflow_sha and uses the action from there, since a local action is looked for in the workspace.

manifest.json lists the path, title and digest of every file pulled; tag and annotations are gone from it.

test-staging pulls the core of this run by its revision.

Caller migration

A request names its packages by annotations; tag is gone. The module repositories move the core commit from tag to org.opencontainers.image.revision in annotations.