Repository navigation
ci: Scale staging only for deploys and always rebuild on deploy - #87
Merged
Merged
Conversation
Staging is kept at zero dynos between deploys to save cost. Production auto-deploys from GitHub have been switched off in Heroku, so this workflow is again the only route to production (staging, smoke test, promote). - Scale staging to one dyno before deploying, and wait for it to respond before the Lost Pixel smoke test. - Scale staging back to zero in a final job that also runs when the deploy, smoke test or promotion fails. - Push an empty commit to Heroku (not GitHub) on each deploy. A dependency update via repository_dispatch leaves master unchanged, so pushing master alone did not rebuild, and promotion copied the old build to production. - Update actions/setup-node from v1 (Node 12 runtime) to v4. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
hkir-dev
approved these changes
Oct 19, 2026
This branch was previously deployed
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
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.
Staging is kept at zero dynos between deploys to save cost. Production auto-deploys from GitHub have been switched off in Heroku, so this workflow is again the only route to production (staging, smoke test, promote).