Repository navigation
Comparing changes
Open a pull request
base repository: dataform-co/dataform
base: 3.1.2
head repository: dataform-co/dataform
compare: 3.1.3
- 15 commits
- 89 files changed
- 7 contributors
Commits on Oct 21, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 59d995a - Browse repository at this point
Copy the full SHA 59d995aView commit details -
fix(cli): use the pinned @dataform/core for JiT compilation (#2392)
* Use the pinned @dataform/core for JiT compilation * Address review comments * Address second round of review comments
Configuration menu - View commit details
-
Copy full SHA for 7344da5 - Browse repository at this point
Copy the full SHA 7344da5View commit details -
Pass JiT compiler arguments as an options object (#2400)
* Pass JiT compiler arguments as an options object * Address review comments
Configuration menu - View commit details
-
Copy full SHA for d203d1f - Browse repository at this point
Copy the full SHA d203d1fView commit details -
fix(cli): emit lineage inputs/outputs on COMPLETE for actions with a …
…BigQuery output and use 3-part actionName (#2399) * fix(cli): gate OpenLineage inputs/outputs on COMPLETE and use 3-part actionName * fix(cli): emit lineage inputs/outputs on COMPLETE for actions with a BigQuery output
Configuration menu - View commit details
-
Copy full SHA for 711f084 - Browse repository at this point
Copy the full SHA 711f084View commit details
Commits on Oct 23, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 04c3878 - Browse repository at this point
Copy the full SHA 04c3878View commit details -
Prefetch npm dependencies for Dependabot PRs (#2405)
* Prefetch npm deps for Dependabot PRs and re-run their failed tests * Skip install scripts when prefetching; allow overriding PR author * Drop re-run workflow; keep this change focused on prefetching * Prefetch only new package versions, one at a time; tolerate PR listing failures * Harden prefetch: timeouts, input validation, token off argv, never fail the build
Configuration menu - View commit details
-
Copy full SHA for 7d3b24a - Browse repository at this point
Copy the full SHA 7d3b24aView commit details -
fix(core): require defaultDataset for incremental Lakehouse tables (#…
…2406) * fix(core): require defaultDataset for incremental Lakehouse tables * refactor(core): move defaultDataset check into validateLakehouseConfig
Configuration menu - View commit details
-
Copy full SHA for a0b91ac - Browse repository at this point
Copy the full SHA a0b91acView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2273460 - Browse repository at this point
Copy the full SHA 2273460View commit details
Commits on Oct 28, 2026
-
fix(cli): disable lineage emitter and display a warning if location i…
…s not set (#2393) * Disable lineage emitter and display a warning if location is not set * address review comments
Configuration menu - View commit details
-
Copy full SHA for 82b2750 - Browse repository at this point
Copy the full SHA 82b2750View commit details -
docs(cli): specify roles/datalineage.producer and processOpenLineageM…
…essage permission (#2412)
Configuration menu - View commit details
-
Copy full SHA for 6f74e8d - Browse repository at this point
Copy the full SHA 6f74e8dView commit details
Commits on Oct 30, 2026
-
support defaultJobLabels and action-level jobLabels (#2344)
* add baJobLabels for all dataform actions * add jobLabels support for `Property graphs`, `Data preparations` and `Bigquery unit tests` action types * Remove unreachable snake_case handling from restoreJobLabelsAsWritten loadActionConfigsFile checks actions.yaml with verifyObjectMatchesProto before restoreJobLabelsAsWritten runs, and that check rejects snake_case keys such as incremental_table, data_preparation and job_labels. Only the camelCase action types can reach this function, so drop the snake_case pairs and the job_labels fallback. * Address PR #2344 review comments * Rethrow job label validation errors when no session is provided setActionJobLabels previously used session?.compileError(...), which silently dropped validation errors when called without a session. Record the error on the session when one is provided, and rethrow it otherwise. * Address follow-up review comments on job labels - Proto comments and configs.md refer to the YAML key `defaultJobLabels` instead of `default_job_labels`. - The `defaultJobLabels` docs now say that actions can't remove a default key, and that the CLI doesn't apply the table's `labels` to the jobs of actions with job labels. - Error messages say "lowercase ASCII letters", since international characters aren't allowed. - main_action_configs_test checks that each case compiles exactly one action. - Test that unit tests without `jobLabels` inherit `defaultJobLabels`. * Check BigQuery's 64-label limit before running, and apply --job-labels to unit tests - A new resolveJobLabels helper decides a job's labels in one place: the action's job labels, or its table's bigqueryLabels if it has none, overridden by --job-labels. - dataform run stops before running anything if an action, or a unit test with --run-tests, would get more than 64 labels (BigQuery's per-job limit). Disabled actions are skipped. - dataform run --run-tests now applies --job-labels to unit-test jobs too. * Return validated job labels instead of mutating the input, and tidy job label tests - validateJobLabels takes unknown input and returns a new object with string values, instead of converting values inside the caller's object. core/main.ts stores the returned labels. Its error now says values may be strings, numbers, or booleans. - The "must be an object" check lives in one helper shared by validateJobLabels and setActionJobLabels. - Built-in assertion configs are built with AssertionConfig.create() instead of a type assertion. - The label constants are no longer exported, and the collections are read-only. - Tests: one test per case instead of loops in test bodies; check where setActionJobLabels reports errors; drop a test that couldn't fail; give jobLabels propagation its own build test; stop modifying the shared RUN_TEST_GRAPH fixture. * Only set table metadata when there is a description, columns or table labels to apply Job labels give every action an actionDescriptor, so checking only that a descriptor exists made `dataform run` patch table metadata (tables.get and tables.patch) for every table, view and incremental table once defaultJobLabels was set. Only call setMetadata when there's a description, column descriptions or table labels for it to apply. * Document job label rules and how --job-labels interacts with other labels Document the allowed job label keys and values, the 32-label limit, reserved keys, built-in assertion inheritance and quoting of numeric YAML values in the proto comments and the configs reference. Describe in the CLI help and README that --job-labels also applies to unit tests run with --run-tests and overrides job and table labels that use the same key, and add the new exit code for jobs over BigQuery's 64-label limit. Rename the two test() API tests that were described as "test command" tests, since `dataform test` has no --job-labels flag.
Configuration menu - View commit details
-
Copy full SHA for 38c5f47 - Browse repository at this point
Copy the full SHA 38c5f47View commit details
Commits on Nov 2, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 3b8ae71 - Browse repository at this point
Copy the full SHA 3b8ae71View commit details -
Configuration menu - View commit details
-
Copy full SHA for d6a2e52 - Browse repository at this point
Copy the full SHA d6a2e52View commit details -
Configuration menu - View commit details
-
Copy full SHA for e42c2cb - Browse repository at this point
Copy the full SHA e42c2cbView commit details -
Configuration menu - View commit details
-
Copy full SHA for d7afead - Browse repository at this point
Copy the full SHA d7afeadView 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.2...3.1.3