ci(docs): wait longer for published SDK availability - #769
Open
cooper-gadd wants to merge 1 commit into
Open
cooper-gadd wants to merge 1 commit into
cooper-gadd wants to merge 1 commit into
Conversation
Co-authored-by: Cooper <126418690+cooper-gadd@users.noreply.github.com>
cooper-gadd
requested review from
Coleary005,
DarrenBaldwin07 and
milldr
as code owners
September 16, 2026 13:16
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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.
Summary
Why
For SDK 0.4.2, npm accepted publication at 12:58:17 UTC on September 16 but the registry version timestamp was 13:01:29. The docs run stopped at 13:01:19, ten seconds too early. Replaying after availability succeeded and opened #768.
Validation
Note
Low Risk
CI timing and npm polling behavior only; no application code, secrets, or permissions changes.
Overview
The update-sdk-examples workflow now waits up to ten minutes for the dispatched
@tembo-io/sdkversion to appear on npm, replacing the previous ~12-attempt (~two minute) loop.The verify step uses an elapsed-time deadline (
SECONDS + 600), caps eachnpm viewcall with--fetch-retries=0and--fetch-timeout=10000, and sets an 11-minute step timeout so the rest of the 15-minute job can still generate and validate examples. Error and status messages were updated to match the longer window; version validation and downstream steps are unchanged.Reviewed by Cursor Bugbot for commit 57f77a6. Bugbot is set up for automated code reviews on this repo. Configure here.