Repository navigation
Comparing changes
Open a pull request
base repository: dataform-co/dataform
base: 3.1.0
head repository: dataform-co/dataform
compare: 3.1.1
- 10 commits
- 97 files changed
- 6 contributors
Commits on Oct 16, 2026
-
refactor(cli): migrate BigQuery integration tests from KMS-encrypted …
…test key to ADC (#2362) * Migrate BigQuery integration tests from KMS-encrypted test key to ADC * Run integration tests as the impersonated dataform-testing service account * Ask for a service account to impersonate in init-creds * Address review comments
Configuration menu - View commit details
-
Copy full SHA for 2a913e6 - Browse repository at this point
Copy the full SHA 2a913e6View commit details
Commits on Oct 19, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 8e5c27f - Browse repository at this point
Copy the full SHA 8e5c27fView commit details -
test: Make bigquery search integration test ignore similarly named le…
…ftover datasets (#2390)
Configuration menu - View commit details
-
Copy full SHA for ee0e469 - Browse repository at this point
Copy the full SHA ee0e469View commit details -
fix(tests): Ensure concurrent test runs do not operate on the same BQ…
… datasets (#2385) * Add randomized suffixes to dataset names; remove stale at test start * Fix JiT integration test tmp dir race: each test owns its resources --------- Co-authored-by: Marcin Biernacik <biernacik@google.com>
Configuration menu - View commit details
-
Copy full SHA for a98a12c - Browse repository at this point
Copy the full SHA a98a12cView commit details
Commits on Oct 20, 2026
-
feat(core): add support for 4-part Lakehouse Catalog targets (#2384)
* feat(protos): add Lakehouse config protobufs and workflow settings mapping * feat(core): support 4-part Lakehouse target normalization and ref/resolve * feat(core): add Lakehouse config support and validations for actions * refactor(core): extract Lakehouse resolution and validation into core/actions/lakehouse.ts * fix(core): apply defaultLakehouseConfig in ref/resolve and reject incomplete Lakehouse refs * fix(core): tighten dependency target parsing and update ref error message * refactor(core): use non-null checks in resolvableAsActionConfigTarget and type ILegacyAssertionConfig.lakehouse
Configuration menu - View commit details
-
Copy full SHA for 1b04df7 - Browse repository at this point
Copy the full SHA 1b04df7View commit details -
fix(cli): Use defaultLocation for BigQuery jobs and datasets in dataf…
…orm run (#2389) * test: Make bigquery search integration test ignore similarly named leftover datasets * Use defaultLocation for BigQuery jobs in dataform run Previously the runner never passed a location to BigQuery jobs, so they ran in the location from .df-credentials.json, ignoring the project's defaultLocation (e.g. 'dataset not found in region EU' for europe-west1 datasets). * fix(cli): Create datasets in defaultLocation and warn on location mismatch * fix(cli): Use defaultLocation for search() and lineage emitter
Configuration menu - View commit details
-
Copy full SHA for 63e11ee - Browse repository at this point
Copy the full SHA 63e11eeView commit details -
Canary test (with GCP bucket) (#2354)
* Add canary test, building the Core bundle and using it to compile a sample project on GCP-based Dataform to ensure cloud backend does not regress
Configuration menu - View commit details
-
Copy full SHA for 4ceca78 - Browse repository at this point
Copy the full SHA 4ceca78View commit details -
fix(cli): remove unused sql and errorMessage OpenLineage facets (#2391)
The Data Lineage API ProcessOpenLineageRunEvent endpoint does not ingest job.facets.sql (SQLJobFacet) or run.facets.errorMessage (ErrorMessageRunFacet); Knowledge Catalog instead resolves the executed SQL query and job status from BigQuery via run.facets.externalQuery. Removing these unused facets avoids sending raw SQL text and task error messages in OpenLineage payloads and aligns the CLI payload builder with Cloud Dataform.
Configuration menu - View commit details
-
Copy full SHA for 471674a - Browse repository at this point
Copy the full SHA 471674aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1513fc7 - Browse repository at this point
Copy the full SHA 1513fc7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5617aa8 - Browse repository at this point
Copy the full SHA 5617aa8View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 3.1.0...3.1.1