chore(deps): upgrade @malloydata/* to 0.0.427 - #958
Merged
girishjeswani merged 1 commit intoAug 3, 2026
Conversation
Run `npm run upgrade-malloy 0.0.427` to move every @malloydata/* pin from 0.0.426 to 0.0.427 across all packages and the root resolutions. malloy-explorer is left unchanged (0.0.427 is not published for it). The reason to adopt 0.0.427 is the BigQuery connector poll-timeout fix (malloydata/malloy#3010): the results poll now honors the connection's configured timeoutMs instead of giving up at a hardcoded ceiling of a few minutes. Long-running materializations (CTAS) need this to finish. DuckDB and pg build knobs already match the new release; lockfile relocked. typecheck:server and typecheck:sdk pass after regenerating API types. Signed-off-by: Girish Jeswani <girish@credibledata.com>
sagarswamirao
approved these changes
Aug 3, 2026
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
2 participants
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.
What
Bumps every
@malloydata/*dependency from0.0.426to0.0.427across all packages and the root resolutions, using the repo's ownnpm run upgrade-malloy 0.0.427.@malloydata/malloy-exploreris left unchanged (0.0.427 is not published for it; the script falls back to its latest published version).Why
0.0.427 includes the BigQuery connector poll-timeout fix (malloydata/malloy#3010). Before that fix,
getQueryResultsUntilCompletepolled to a hardcoded ceiling of a few minutes and failed long queries with "The query did not complete before 120000ms", ignoring the connection's configuredtimeoutMs. After the fix the poll honorstimeoutMs, so long-running materializations (a CTAS such as anML.GENERATE_TEXTpersist) can complete.I validated the connector behavior directly against BigQuery: on 0.0.426 a roughly 10 minute CTAS fails at about 6 minutes regardless of a 20 minute
timeoutMs; on 0.0.427 the same query is polled for the full configured window and completes.Changes
@malloydata/*pins0.0.426->0.0.427inpackage.json(resolutions),packages/server,packages/sdk,packages/create-malloy-packagebun.lockrelockedpgbuild knobs already matched the new release (no change)Testing
typecheck:serverandtypecheck:sdkpass (aftergenerate-api-types)