Skip to content

chore(deps): bump jvspatial 0.0.11 -> 0.0.12#71

Open
eldonm wants to merge 1 commit into
mainfrom
chore/bump-jvspatial-0.0.12
Open

chore(deps): bump jvspatial 0.0.11 -> 0.0.12#71
eldonm wants to merge 1 commit into
mainfrom
chore/bump-jvspatial-0.0.12

Conversation

@eldonm

@eldonm eldonm commented Jul 7, 2026

Copy link
Copy Markdown
Member

Bumps the jvspatial pin to 0.0.12 (just released) across pyproject.toml, requirements.txt, and requirements-all.txt.

Why

0.0.12 ships:

  • Postgres translator hits the real entity/id/tenant_id columns (using <collection>_entity_idx) instead of JSONB path extraction — every .find() auto-injects an entity filter, so this is a broad query-planning win.
  • JVSPATIAL_OBSERVABILITY_ENABLED / JVSPATIAL_SLOW_QUERY_MS registered in the env allowlist.

Both are backward-compatible bugfix/config changes.

Test plan

  • pre-commit run clean.
  • CI test-jvagent installs jvspatial 0.0.12 and runs the suite (records the resolved version per the pyproject note).

Independent of #70 (queue_task priority fix) — different files, no conflict.

🤖 Generated with Claude Code

Pick up the postgres translator column-index fix (entity/id/tenant_id hit the
real indexed columns, not JSONB paths) + observability env keys released in
jvspatial 0.0.12. Bumped in pyproject.toml, requirements.txt, requirements-all.txt.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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