From 81a2970e6cf8be614941f33e47e9e2b8c04312c0 Mon Sep 17 00:00:00 2001 From: Wuesteon Date: Mon, 8 Dec 2025 23:02:40 +0100 Subject: [PATCH] docs: add tag naming convention for mana-core-auth MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add documentation explaining the correct tag format for mana-core-auth deployments. Using `auth-staging-*` instead of `mana-core-auth-staging-*` causes the CD workflow to fail. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- docs/STAGING_DEPLOYMENT_ISSUES.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/STAGING_DEPLOYMENT_ISSUES.md b/docs/STAGING_DEPLOYMENT_ISSUES.md index 2a72310d6..1dd0e283d 100644 --- a/docs/STAGING_DEPLOYMENT_ISSUES.md +++ b/docs/STAGING_DEPLOYMENT_ISSUES.md @@ -134,6 +134,18 @@ The CD workflow (`.github/workflows/cd-staging-tagged.yml`) now: 2. Updates the `.env` file on staging server 3. docker-compose reads from `.env` +### Tag Naming Convention + +Tags must follow the exact project name as defined in the CD workflow: + +| Project | Correct Tag Format | Wrong Format | +|---------|-------------------|--------------| +| mana-core-auth | `mana-core-auth-staging-v1.0.0` | `auth-staging-v1.0.0` | +| chat | `chat-staging-v1.0.0` or `chat-all-staging-v1.0.0` | - | +| todo | `todo-staging-v1.0.0` or `todo-all-staging-v1.0.0` | - | + +**Note**: Using the wrong tag format (e.g., `auth-staging-*` instead of `mana-core-auth-staging-*`) will cause the workflow to fail because it won't find the correct Dockerfile path. + ### Verifying Deployment ```bash