Build API from its deployed runtime revision - #346
Merged
Conversation
Constraint: Release metadata can advance while a prior API image remains deployed.\nRejected: Force every deploy to rebuild the API | unnecessary builds would erase the lean deployment lane.\nConfidence: high\nScope-risk: narrow\nDirective: Compute API scope from API_RUNTIME_REVISION, not the overall deploy metadata commit.\nTested: deploy contract test, classifier regression test, env authority test, git diff check\nNot-tested: GitHub-hosted deployment until merged
Constraint: Deployment workflow fixes need validation before they reach main.\nRejected: Rely only on post-merge main CI | defects would be discovered after merge.\nConfidence: high\nScope-risk: narrow\nDirective: Keep deploy workflow, wrapper, and contract-test paths in the PR trigger.\nTested: deploy contract test, classifier test, git diff check\nNot-tested: GitHub path-filter trigger until push
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
Why
A metadata-only rollout can advance COMMIT_SHA while reusing the prior API image. Subsequent deploys must compare API changes from the revision embedded in the running image or they can permanently skip an API asset update.
Verification