Skip to content

chore: sync main into dev (0.1.8rc11 / jvspatial 0.0.18) - #228

Merged
eldonm merged 5 commits into
devfrom
chore/sync-dev-with-main-rc11
Sep 13, 2026
Merged

eldonm merged 5 commits into
devfrom
chore/sync-dev-with-main-rc11

Conversation

@eldonm

@eldonm eldonm commented Sep 13, 2026

Copy link
Copy Markdown
Member

Summary

  • Bring #226 (jvspatial==0.0.18, 0.1.8rc11) from main onto dev
  • Pair with #227 that puts #222#225 onto main

Test plan

  • CI green
  • After merge: dev has __version__ == 0.1.8rc11 and jvspatial==0.0.18

Made with Cursor

eldonm and others added 5 commits September 10, 2026 16:23
Unlock hub-node derive mode and neighbour SQL pushdown for hosts that
pin jvagent and jvspatial in lockstep (Integral Phase A).
Concurrent waiters hydrate distinct Python instances after serialized
create; object-identity checks flake under full-suite pre-push.
chore(deps): require jvspatial 0.0.18 (0.1.8rc11)
`main` received #226; `dev` received #222#225. Bring the pin onto
`dev` so the next integration work is not still on 0.0.17 / rc10.
@eldonm eldonm changed the title chore: sync main into (0.1.8rc11 / jvspatial 0.0.18) chore: sync main into dev (0.1.8rc11 / jvspatial 0.0.18) Sep 13, 2026
@eldonm eldonm self-assigned this Sep 13, 2026
@eldonm
eldonm merged commit 01be1d3 into dev Sep 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant