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: operatorstack/modelgraph
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: feat/composable-model-graph
Choose a base ref
...
head repository: operatorstack/modelgraph
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 3 commits
  • 6 files changed
  • 2 contributors

Commits on Jun 5, 2026

  1. Merge pull request #1 from operatorstack/feat/composable-model-graph

    Composable Model Graph library
    bigboateng authored Jun 5, 2026
    Configuration menu
    Copy the full SHA
    1497f0f View commit details
    Browse the repository at this point in the history

Commits on Jun 8, 2026

  1. Make repo root importable as a git dependency (#2)

    Name the root package `modelgraph` (was a confusing `composable-model-graph`
    leftover that collided with the sibling repo) and expose the built core via
    root `exports`/`main`/`types` pointing at `packages/core/dist`. Add a
    `prepare` script (`tsc -b packages/core`) so installing this repo as a
    GitHub-URL dependency builds core's dist on install without publishing to npm.
    
    Co-authored-by: Cursor <cursoragent@cursor.com>
    bigboateng and cursoragent authored Jun 8, 2026
    Configuration menu
    Copy the full SHA
    68649ea View commit details
    Browse the repository at this point in the history

Commits on Jun 9, 2026

  1. feat(core): add optional branch/merge connections to model graph (#3)

    Transforms can now be connected as a branch/merge graph via an optional
    `connections` list, while a transforms-only config still runs as a straight
    line (full back-compat). A transform runs once every transform feeding it has
    produced output; transforms whose inputs are all ready run together, and a
    merge transform receives the ordered list of its feeders' outputs. Cycles are
    rejected; repeating a run stays a concern for the layer above the graph.
    
    Co-authored-by: Cursor <cursoragent@cursor.com>
    bigboateng and cursoragent authored Jun 9, 2026
    Configuration menu
    Copy the full SHA
    982728e View commit details
    Browse the repository at this point in the history
Loading