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.0.58
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.0.59
Choose a head ref
  • 8 commits
  • 13 files changed
  • 1 contributor

Commits on May 26, 2026

  1. Configuration menu
    Copy the full SHA
    8506ed5 View commit details
    Browse the repository at this point in the history

Commits on May 28, 2026

  1. Configuration menu
    Copy the full SHA
    d59249e View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    706c847 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    26a2a81 View commit details
    Browse the repository at this point in the history

Commits on Jun 2, 2026

  1. Add JiT compilation support for assertion actions (#2193)

    Adds JIT_COMPILATION_TARGET_TYPE_ASSERTION alongside the existing
    TABLE / OPERATION / INCREMENTAL_TABLE target types, plus a matching
    JitAssertionResult { string query } proto and a jitCompileAssertion()
    dispatcher in core/jit_compiler.ts. Assertions reuse SqlActionJitContext
    since AssertionContext implements IActionContext, and the result is a
    single SELECT query string (matching the existing
    JitAssertionResult = string alias in core/actions/assertion.ts).
    rafal-hawrylak authored Jun 2, 2026
    Configuration menu
    Copy the full SHA
    510f086 View commit details
    Browse the repository at this point in the history
  2. Fix caller-file error (#2177) and enforce Core/CLI version match (#2191)

    vm2 3.11.3 strips file paths from V8 CallSite objects inside the sandbox,
    so `getCallerFile()` in @dataform/core can no longer resolve the current
    file from the stack. Track it via a host-side stack exposed through
    `__df_enter`/`__df_exit`/`__df_current` sandbox helpers and read it through
    a getter on `global.__dataform_current_file`.
    
    For @dataform/core <= 3.0.56 (no global fallback in getCallerFile), patch
    the bundle text at load time to consult the global. Gated on the installed
    Core version so newer bundles are never touched.
    
    Add a CLI/Core compatibility check: reject installed Core whose major
    differs from the CLI's, or whose minor is below the CLI's minor. Resolve
    the installed Core's version by running
    `require("@dataform/core").version` inside the index-generator vm so any
    install layout (package.json, workflow_settings.yaml stateless install,
    JiT) reports the version actually loaded. The error tells the user the
    exact `dataformCoreVersion:` line to set in `workflow_settings.yaml`.
    Skipped when the CLI version can't be determined (unbundled local dev).
    
    Mirror the same wrapper pattern in `testing/run_core.ts`.
    
    Add `compile rejects @dataform/core with incompatible version` test in
    `cli/index_compile_test.ts` that drives the workflow_settings.yaml
    stateless install path with dataformCoreVersion: "2.9.0" (latest 2.x on
    the registry) to exercise the real `npm i` install flow.
    
    Add `compile succeeds with @dataform/core <= 3.0.56 via caller-file shim`
    test that installs @dataform/core@3.0.50 and asserts the compiled action's
    `fileName` matches the source path, end-to-end proving the bundle-text
    patch and host-side file stack restore getCallerFile under vm2 3.11.3.
    rafal-hawrylak authored Jun 2, 2026
    Configuration menu
    Copy the full SHA
    bb75716 View commit details
    Browse the repository at this point in the history
  3. Raise default compile timeout to 60s and improve timeout error message (

    #2192)
    
    Default compilation timeout was 30s. Bump to 60s so larger projects
    don't hit it on a single compile pass.
    
    Extends the "Compilation timed out" error to point at --timeout with
    concrete examples (--timeout=2m, --timeout=1h) so users can self-mitigate
    without reading docs.
    rafal-hawrylak authored Jun 2, 2026
    Configuration menu
    Copy the full SHA
    529f14c View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    37dba63 View commit details
    Browse the repository at this point in the history
Loading