From b04616ffba4e796bf0c374e7db5022adc09c08b2 Mon Sep 17 00:00:00 2001 From: Eldon Marks Date: Sat, 3 Oct 2026 09:58:07 -0400 Subject: [PATCH] chore(deps): pin jvspatial 0.1.1 --- .planning/reference/jvspatial-integration.md | 4 ++-- AGENTS.md | 2 +- CHANGELOG.md | 4 ++++ pyproject.toml | 2 +- requirements-all.txt | 2 +- requirements.txt | 2 +- 6 files changed, 10 insertions(+), 6 deletions(-) diff --git a/.planning/reference/jvspatial-integration.md b/.planning/reference/jvspatial-integration.md index 13f50a4c..6ca92315 100644 --- a/.planning/reference/jvspatial-integration.md +++ b/.planning/reference/jvspatial-integration.md @@ -7,7 +7,7 @@ ## 1. Where jvspatial lives - **Source**: `/Users/eldonmarks/Briefcase/dev/jv/jvspatial` (sibling directory in this workspace). -- **Pip install**: [`pyproject.toml`](../../pyproject.toml) and both requirements files temporarily pin the exact patched jvspatial Git commit. Replace all three refs with the published patched version before publishing jvagent; a fresh `pip install -e '.[test]'` must resolve the reviewed commit in `jvspatial`'s `direct_url.json`. +- **Pip install**: [`pyproject.toml`](../../pyproject.toml) and both requirements files pin the same published jvspatial release. Verify the installed `jvspatial` version and package origin in a fresh environment before updating this pin. - **Own docs**: jvspatial has its own [`README.md`](../../../jvspatial/README.md) and [`SPEC.md`](../../../jvspatial/SPEC.md). Treat those as authoritative for anything below. --- @@ -175,7 +175,7 @@ Things jvagent **owns**: ## 5. Version policy -- Minimum required jvspatial: pinned in [`pyproject.toml`](../../pyproject.toml) as `jvspatial==X.Y.Z`. Current: `==0.0.21`. +- Required jvspatial: pinned in [`pyproject.toml`](../../pyproject.toml) as `jvspatial==0.1.1`. - When jvspatial introduces breaking changes (e.g., walker API rename, persistence shape change), bump the pin and update this section. - When adding a new dependency on a jvspatial feature, document the symbol + version it was introduced in. Helps downstream consumers know the floor. - Rationale: [`adr/0006-jvspatial-dependency.md`](../adr/0006-jvspatial-dependency.md). diff --git a/AGENTS.md b/AGENTS.md index 759c0777..5553ee28 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -10,7 +10,7 @@ Keep agent guidance in this file or the nearest scoped `AGENTS.md`. Do not creat A modular AI-agent platform built on [jvspatial](.planning/reference/jvspatial-integration.md)'s object-spatial graph framework. -**jvspatial security compatibility:** keep `pyproject.toml`, `requirements.txt`, and `requirements-all.txt` on the same published jvspatial version (`0.1.0`), and verify a fresh install when updating the pin. jvspatial rejects undeclared instance attributes on entity subclasses: declare persisted fields with `attribute(...)` and runtime-only underscore state with Pydantic `PrivateAttr`. See [the integration reference](.planning/reference/jvspatial-integration.md) and [action authoring](.planning/reference/action-authoring.md). +**jvspatial security compatibility:** keep `pyproject.toml`, `requirements.txt`, and `requirements-all.txt` on the same published jvspatial version (`0.1.1`), and verify a fresh install when updating the pin. jvspatial rejects undeclared instance attributes on entity subclasses: declare persisted fields with `attribute(...)` and runtime-only underscore state with Pydantic `PrivateAttr`. See [the integration reference](.planning/reference/jvspatial-integration.md) and [action authoring](.planning/reference/action-authoring.md). - An *app* declares one or more *agents* in YAML. - Each agent owns a graph of *actions* (plugins) plus a per-user memory subgraph (`User → Conversation → Interaction`). diff --git a/CHANGELOG.md b/CHANGELOG.md index a6c7b671..fa3c9986 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,10 @@ and this project adheres to [PEP 440](https://peps.python.org/pep-0440/) / ## [Unreleased] +### Changed + +- Pin the published `jvspatial==0.1.1` release across package metadata and requirements, incorporating PostgreSQL index naming and schema bootstrap fixes. + ## [0.1.8rc19] - 2026-09-27 ### Added diff --git a/pyproject.toml b/pyproject.toml index e9203606..1247fb53 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -30,7 +30,7 @@ classifiers = [ dependencies = [ "aiohttp>=3.9.0", - "jvspatial==0.1.0", + "jvspatial==0.1.1", "pydantic[email]>=2.13.5", "python-dotenv>=1.0.0", "pyyaml>=6.0.0", diff --git a/requirements-all.txt b/requirements-all.txt index b449925d..b96de9d6 100644 --- a/requirements-all.txt +++ b/requirements-all.txt @@ -6,7 +6,7 @@ # Must stay in sync with [project] dependencies in pyproject.toml — # enforced by tests/test_requirements_sync.py. aiohttp>=3.9.0 -jvspatial==0.1.0 +jvspatial==0.1.1 python-dotenv>=1.0.0 pyyaml>=6.0.0 httpx>=0.27.0 diff --git a/requirements.txt b/requirements.txt index c370707b..526b5f29 100644 --- a/requirements.txt +++ b/requirements.txt @@ -3,7 +3,7 @@ # Test-only deps (incl. Docling for PageIndex): pyproject.toml # [project.optional-dependencies] test — install with: pip install -e ".[test]" aiohttp>=3.9.0 -jvspatial==0.1.0 +jvspatial==0.1.1 pydantic[email]>=2.13.5 python-dotenv>=1.0.0 pyyaml>=6.0.0