Skip to content

ci(deploy): add NATS to deploy.yml test gate (unwedge deploy pipeline)#165

Merged
mastermanas805 merged 1 commit into
masterfrom
ci/deploy-nats-service-2026-05-23
May 23, 2026
Merged

ci(deploy): add NATS to deploy.yml test gate (unwedge deploy pipeline)#165
mastermanas805 merged 1 commit into
masterfrom
ci/deploy-nats-service-2026-05-23

Conversation

@mastermanas805
Copy link
Copy Markdown
Member

Fixes the broken deploy pipeline. #163 merged the TestQueue_* coverage tests, which provision against localhost:8222 (NATS monitoring). ci.yml got a NATS service in #163, but deploy.yml has its own go test ./... -short -p 1 gate with only postgres+redis — so it 503s on TestQueue_* and the deploy aborts before building. Result: master is merged but prod stayed on the old SHA (verified: live /healthz=afa0335, master=3b549ed).

Mirrors the ci.yml NATS step into deploy.yml. Once merged, the triggering deploy run has NATS available → test gate passes → prod deploys.

🤖 Generated with Claude Code

deploy.yml runs its own 'go test ./... -short -p 1' gate with postgres+redis
but no NATS. After #163 merged the TestQueue_* coverage tests to master, this
gate 503s on them and the deploy aborts before build/push — wedging the deploy
pipeline for every merge to master. Mirror the ci.yml NATS step here.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mastermanas805 mastermanas805 merged commit cfc9ecc into master May 23, 2026
13 checks passed
@mastermanas805 mastermanas805 deleted the ci/deploy-nats-service-2026-05-23 branch May 23, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant