feat(ci): deploy to prod when a release is published#218
Merged
Conversation
Mirrors the now-working deploy-dev pipeline (ARM64 image build, ECS migrate task, service rollout) with release semantics: triggers on release published, refuses to ship a commit without green CI, tags the prod image with both the release tag and the SHA, and reports via the run summary. Uses the checkin-deploy-prod OIDC role and the production GitHub environment, so protection rules can be layered on later. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
#219) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Cross-PR dependency from #249 (event-reminder idempotency): #249 adds migration |
jee7s
approved these changes
Jun 17, 2026
❌ Dev deploy failedCommit
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Deploy prod, triggered by publishing a GitHub release in this repo. It mirrors the now-working
deploy-dev.ymlstep-for-step (so fixes #211/#212/#215/#217 all carry over), with release semantics:release: [published]— cut a release withgh release create v1.2.3 --target main --generate-notesand it ships. Drafts don't fire; publishing them does.Run Testscheck isn't green (releases can technically be cut from any commit).checkin-prod:<sha>andcheckin-prod:<release-tag>for traceability/rollback.checkin-prodECR/cluster/service/task families,checkin-deploy-prodOIDC role, https://ops.innovationtreehouse.org. (Verified all exist in AWS, and thecheckin-prod/*secrets all have values.)productionis declared, so required-reviewer protection can be layered on in repo settings whenever desired — no workflow change needed.Rollback story: re-publish (or re-run the deploy of) the previous release, or
update-serviceto the prior task-def revision.🤖 Generated with Claude Code