From 37fadd878b2a9c0ed844764cb77cc723d2fc6352 Mon Sep 17 00:00:00 2001 From: Adam Wright Date: Thu, 23 Jul 2026 10:32:48 -0400 Subject: [PATCH] chore: bump Reactome graph DB to Release97 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Diagrams (~/reactome-diagrams/97) are Release 97 but the compose pinned the DB to Release96, so ~85 diagram 'following' pairs referenced R97 reactions absent from the R96 DB (e.g. R-HSA-9980233 "PIP3 activates mTORC2") — a version-skew gap, not the diagram encoding connectivity the DB lacks. At matching release, diagram following == neo4j precedingEvent exactly (0 diagram-only pairs). The DB is baked into the image at /var/lib/neo4j/data; the neo4j_data:/data volume is vestigial (empty), so the tag bump serves R97 with no volume changes. Version sentinel test reports v97. Co-Authored-By: Claude Fable 5 --- docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index 3290c54..713977d 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -4,7 +4,7 @@ services: neo4j: # Bump this tag when a new Reactome release lands; the version sentinel # test in tests/test_reactome_version.py records what we ran against. - image: public.ecr.aws/reactome/graphdb:Release96 + image: public.ecr.aws/reactome/graphdb:Release97 container_name: reactome-neo4j ports: - "7474:7474" # HTTP