Releases

Releases

GHCR image tags and how releases are cut. Deep: releases.md · CHANGELOG.

Current image

docker pull ghcr.io/hypersdk/zyaiqaagent:v0.4.0
docker pull ghcr.io/hypersdk/zyaiqaagent:latest

docker run --rm --env-file .env ghcr.io/hypersdk/zyaiqaagent:v0.4.0 test --grep @smoke
docker run --rm -p 8080:8080 --env-file .env \
  ghcr.io/hypersdk/zyaiqaagent:v0.4.0 serve --port 8080 --host 0.0.0.0

Entrypoint is zyvor-qa — any subcommand works as container args.

Pin vX.Y.Z in CI/Action (hypersdk/ZyAIQAAgent@v0.4.0); :latest is not reproducible.

If the package is private: docker login ghcr.io with read:packages.

What a tag does

Push v*.*.* → workflow builds docker/Dockerfile, pushes GHCR (:tag + :latest), creates GitHub Release notes.

# Bump pyproject.toml / package.json first
git tag v0.4.1
git push hypersdk v0.4.1
# or
gh release create v0.4.1 --repo hypersdk/ZyAIQAAgent --generate-notes

One-off Pod

kubectl run zyvor-qa --image=ghcr.io/hypersdk/zyaiqaagent:v0.4.0 \
  --env="ZYVOR_BASE_URL=https://zyvor.dev" \
  -- serve --port 8080 --host 0.0.0.0

Full Deployment/CronJob: Deploy and Releases · Agent CI and Kubernetes.

Related: External CI/CD · action.yml