Add Package

If the package is deployable, add a Dockerfile.

2. Update scripts/release-helpers.sh

This file contains all package metadata. Three places must be updated:

a. ALL_PACKAGES variable (line ~19)

Add the package name to the space-separated list:

ALL_PACKAGES="agent-creator agent-runner orchestrator-agent console-backend console-frontend ringier-a2a-sdk client-slack client-slack-frontend client-email <new-package>"

b. pkg_dir() function

Add a case entry mapping package name → directory:

    <new-package>)           echo "packages/<new-package>" ;;

c. pkg_type() function

Add a case entry declaring the package type (python or node):

    # Add to the correct case group:
    # node packages: console-frontend|client-slack-frontend|client-slack|client-email|<new-package>
    # python packages: agent-creator|agent-runner|orchestrator-agent|console-backend|ringier-a2a-sdk|<new-package>

3. Update justfile

Only required if the package has a Dockerfile (is buildable/deployable):

a. Add an image variable (top of file, ~line 30)

img_<new_package> := registry + "/nannos-<new-package>"

Variable name uses underscores; image name uses hyphens.

b. Add to _buildable_packages list (~line 46)

_buildable_packages := "agent-creator agent-runner orchestrator-agent console-backend console-frontend client-slack client-slack-frontend client-email <new-package>"

c. Add case in pkg-image recipe (~line 62)

      <new-package>)    echo "{{ img_<new_package> }}" ;;

d. (Optional) Add case in pkg-deploy recipe

Only if the k8s deployment name differs from the package name:

      <new-package>) echo "<deploy-name>" ;;

4. Kubernetes Manifests

Update the example-k8s-deployment/ directory with the necessary manifests to deploy the new package as a service. Look through the existing files to see the pattern.

!! important: If there is a gitops folder symlinked in this repo root this means this developer is managing a k8s cluster: See gitops/AGENTS.md - it has instruction on how to construct the necessary k8s manifests and add them to the FluxCD gitops.

5. Verify

Run these commands to confirm the package is correctly registered:

# Should list your new package with its version
just pkg-version <new-package>

# Should show the package in the changed list (since it has no release tag yet)
just changed

# If buildable, verify the image name resolves
just pkg-image <new-package>

Checklist Summary