Repository navigation
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
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.0.67
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: dataform-co/dataform
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.0.68
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 4 commits
- 21 files changed
- 1 contributor
Commits on Sep 2, 2026
-
Support ref() and DAG dependencies in PropertyGraph (#2258)
* Support ref() and DAG dependencies in PropertyGraph Extends PropertyGraph to accept `ref: [dataset, table]` in place of a bare table name for `nodeTables` and `edgeTables`. Refs resolve through the same `Session.resolve` path used by tables and operations so the graph action inherits the standard dependency edges. The resolved dependencies land on the compiled action's `dependencyTargets` which makes the executor run source tables before the graph DDL. Ref resolution respects schema suffixes and database overrides so a graph declared with `ref: [authors]` in a suffixed workspace still targets the suffixed dataset. Lock-in tests cover the resolved-DDL output for named refs, dataset-scoped refs, mixed literal-and-ref entries, and the error surface when a ref points at a nonexistent action. * Extract session.resolveTarget helper Adds session.resolveTarget(ref) that returns the structured Target and refactors session.resolve to delegate to it. PropertyGraph.resolveRefIntoDataSource now uses the shared helper instead of duplicating the find plus Declaration branch plus finalize schema/db/name logic. * Add graph.yaml surface for assertion dependencies Adds depend_on_dependency_assertions on PropertyGraphConfig and include_dependent_assertions on DataSourceRef. The graph action reads the config-level flag into this.dependOnDependencyAssertions and propagates the per-ref flag onto the pending Target so checkAssertionsForDependency can merge them the same way it does for tables.
Configuration menu - View commit details
-
Copy full SHA for e42d210 - Browse repository at this point
Copy the full SHA e42d210View commit details
Commits on Sep 3, 2026
-
Fix "index.js" mis-attribution of ref/resolve compilation errors (#2271)
Session.resolve raises compileError() with no explicit file path, so it falls through to utils.getCallerFile(). Under vm2 >= 3.11.3, V8 CallSite objects inside the sandbox no longer carry file paths, and the global.__dataform_current_file fallback installed by the CLI wrapper is scoped to module load -- by the time a sqlx action's callback executes (during Session.compile), that global has been restored to the outer "index.js" sandbox entry. Every ref/resolve failure was consequently blamed on "index.js" instead of the sqlx file (see #2266). Track the current action's file on the Session while its callback is being compiled, and let compileError() prefer it over the caller-file fallback. No behavior change when compileError is called with an explicit path.
Configuration menu - View commit details
-
Copy full SHA for 843121b - Browse repository at this point
Copy the full SHA 843121bView commit details -
Add CLI runtime coverage and E2E integration test for PropertyGraph (#…
…2268) * Add CLI runtime coverage and E2E integration test for PropertyGraph Wires PropertyGraph into the CLI runtime paths that were missing from the initial action plumbing: - `dataform prune` includes PropertyGraph actions in tag and dependency filtering - `dataform run` prints graph actions through the console progress reporter with the same status lines as tables - `dataform run --dry-run` skips PROPERTY GRAPH DDL because BigQuery dry-run requires the referenced NODE and EDGE tables to physically exist which is not true on a fresh workspace Adds an integration test at tests/integration/property_graph_project that compiles a three-table fixture (authors, books, wrote) plus one LibraryGraph over them, executes it against BigQuery, asserts all four actions succeed, verifies the graph is created after the source tables by timestamp, and confirms the graph appears in INFORMATION_SCHEMA.PROPERTY_GRAPHS. The test drops the graph and dataset before and after the run since `cleanWarehouse` does not know about property graphs. * Address PR feedback: drop property-graph dry-run skip and trim fixture Remove the shouldSkipPropertyGraphDryRun helper and its test suite so property graphs behave like tables under dry-run. Trim the integration fixture workflow_settings.yaml to defaultDataset only and rely on the BigQuery adapter credentials fallback for project and location.
Configuration menu - View commit details
-
Copy full SHA for b7bbf98 - Browse repository at this point
Copy the full SHA b7bbf98View commit details -
Configuration menu - View commit details
-
Copy full SHA for d62ba04 - Browse repository at this point
Copy the full SHA d62ba04View commit details
Loading
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.0.67...3.0.68