ci: add manual den-api redeploy lever to EE publish workflow - #3510
Closed
benjaminshafii wants to merge 1 commit into
Closed
ci: add manual den-api redeploy lever to EE publish workflow#3510benjaminshafii wants to merge 1 commit into
benjaminshafii wants to merge 1 commit into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
benjaminshafii
enabled auto-merge (squash)
August 4, 2026 15:22
auto-merge was automatically disabled
August 5, 2026 04:50
Pull request was closed
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.
Why
Today's incident (#3507): the den-api fix merged to
devat 14:50 UTC and its image published immediately, but the hosted den-api kept serving the old handoff exchange schema — verified via the production OpenAPI (DesktopHandoffExchangeResponsestill[token, user], noorganization). Gateway auto-redeploys on dev pushes; den-api has no deploy lever at all, so client fixes that depend on server changes silently stall.What
workflow_dispatchinputredeploy_den_api(defaultfalse).redeploy-den-apijob mirroring the existing gateway job: POSTs a Render deploy for the den-api service (RENDER_DEN_API_SERVICE_ID+RENDER_API_KEY), gracefully skips with a summary notice when credentials are absent.den-db-migrate.yml, so recycling den-api onto the current published dev image is safe. Full den-api dev CD stays a deliberate follow-up per the existing comment.Usage
Actions -> Publish EE Artifacts -> Run workflow -> check
redeploy_den_api.Validation
python3 -c "import yaml; yaml.safe_load(...)"— YAML parses.Note:
RENDER_DEN_API_SERVICE_IDmust be added to repo secrets before the lever does anything (job no-ops with a notice until then).