Harden deploy.yml: hermetic builds + build/deploy separation#3
Merged
Conversation
Remove npm cache from deploy builds. Split all 3 deploy jobs into isolated build (zero secrets) and deploy (secrets only after build) jobs. Most critically, deploy-supabase's 10+ secrets are now isolated from npm install and build steps. Matches CopilotKit/CopilotKit PR #4774 supply chain hardening pattern.
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
1 participant
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.
Summary
cache: npmfrom all 3 deploy builds so each does a coldnpm ci(hermetic)The deploy-supabase split is the most critical — previously 10+ secrets were available during
npm ciandnpm run build.Applies the same supply chain hardening patterns from CopilotKit/CopilotKit PR #4774.
Test plan