fix: adding/removing db does not trigger rebuild

[NathanFlurry]

No description provided.

[graphite-app]

Your org requires the Graphite merge queue for merging into main

Add the label “merge queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

[NathanFlurry]

• fix: adding/removing db does not trigger rebuild #237 : 4 dependent PRs (#220 , #238 , #239 and 1 other) 👈
• fix: allow for mutiple node instances across different processes #236
• fix: RuntimeError meta not persisting #234
• chore: rework caching to isolate hashes to each step id #233
• chore: print stack trace for internal errors, print value for unreachable #232
• chore: write build state at every checkpoint #231
• fix: false positives on compare hash logic in batches #230
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NathanFlurry and the rest of your teammates on Graphite

[graphite-app]

Merge activity

• Mar 15, 8:29 AM EDT: NathanFlurry added this pull request to the Graphite merge queue.
• Mar 15, 8:50 AM EDT: NathanFlurry removed this pull request from the Graphite merge queue.
• Mar 15, 9:52 AM EDT: @NathanFlurry started a stack merge that includes this pull request via Graphite.
• Mar 15, 10:06 AM EDT: Graphite rebased this pull request as part of a merge.
• Mar 15, 10:07 AM EDT: @NathanFlurry merged this pull request with Graphite.