Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dataform-co/dataform
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3.1.0
Choose a base ref
...
head repository: dataform-co/dataform
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.1.1
Choose a head ref
  • 10 commits
  • 97 files changed
  • 6 contributors

Commits on Oct 16, 2026

  1. 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
    mbiernacik authored Oct 16, 2026
    Configuration menu
    Copy the full SHA
    2a913e6 View commit details
    Browse the repository at this point in the history

Commits on Oct 19, 2026

  1. Configuration menu
    Copy the full SHA
    8e5c27f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    ee0e469 View commit details
    Browse the repository at this point in the history
  3. 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>
    Ford544 and mbiernacik authored Oct 19, 2026
    Configuration menu
    Copy the full SHA
    a98a12c View commit details
    Browse the repository at this point in the history

Commits on Oct 20, 2026

  1. 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
    SergikL authored Oct 20, 2026
    Configuration menu
    Copy the full SHA
    1b04df7 View commit details
    Browse the repository at this point in the history
  2. 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
    apilaskowski authored Oct 20, 2026
    Configuration menu
    Copy the full SHA
    63e11ee View commit details
    Browse the repository at this point in the history
  3. 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
    Ford544 authored Oct 20, 2026
    Configuration menu
    Copy the full SHA
    4ceca78 View commit details
    Browse the repository at this point in the history
  4. 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.
    rafal-hawrylak authored Oct 20, 2026
    Configuration menu
    Copy the full SHA
    471674a View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    1513fc7 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    5617aa8 View commit details
    Browse the repository at this point in the history
Loading
⌂ 换网址