Skip to content

Releases: aws/graph-explorer

Release 3.0.3

04 May 22:07
dac0d7c

Choose a tag to compare

This patch release blocks cross-origin requests by default, improves performance for larger schemas, adds inferred edge connections in search and expansion, and adds a diagnostic logging setting.

  • Schema Explorer — edge connections are now inferred from graph exploration, so the Schema Explorer shows relationships discovered through search and neighbor expansion without waiting for the database summary API
  • Performance — schema operations are significantly faster for graphs with many vertex or edge types, reducing unnecessary re-renders when the schema is already up to date
  • New feature — a diagnostic logging toggle in settings enables verbose console logging at runtime, even in production builds, for easier troubleshooting
  • Documentation — getting started restructured as a hands-on tutorial, new configuration reference, new Neptune public endpoints guide, new architecture documentation
  • Infrastructure — hardened Docker image and CI workflows, migrated to oxfmt and oxlint for faster formatting and linting, TypeScript upgraded to 6.0, proxy server runs natively without a build step

Cross-Origin Request Blocking

The proxy server now blocks cross-origin requests by default instead of allowing all origins. Since the proxy server serves both the API and the UI from the same origin in all standard deployments (Docker, SageMaker, ECS Fargate), CORS is not needed.

If you serve the UI from a different origin than the proxy server, set the PROXY_SERVER_CORS_ORIGIN environment variable to the UI origin. See the Security documentation for details.

All Changes

Release 3.0.2

21 Apr 00:36
faf49d2

Choose a tag to compare

This patch release fixes a bug where schema sync did not automatically trigger when switching connections and adds a new configuration option for controlling allowed origins.

  • Bug fix — schema sync now automatically triggers when switching to a connection that has no cached schema
  • Configuration — new PROXY_SERVER_CORS_ORIGIN environment variable lets you explicitly control which origins are allowed to connect to the proxy server. See the Security documentation for details.

All Changes

Release 3.0.1

13 Apr 21:49
012c9e6

Choose a tag to compare

This patch release improves error handling, refactors the proxy server for testability, and hardens the application protection mechanisms. Error messages surface richer diagnostics — status codes, response bodies, and cause chains — so troubleshooting is more useful. We also upgraded to Vite 8, cutting build time by 60% and bundle size by 5%.

  • Bug fixes — new empty state when no connections are configured instead of misleading "No Schema Available", Docker entrypoint now respects custom config directories (thanks @theneelshah!), Podman container permissions fix
  • Error handling — the error details dialog now surfaces status codes, response bodies, and cause chains so you can diagnose issues without digging through logs. Invalid proxy requests return proper 400 errors instead of cryptic 500s. Connection failures and CORS mismatches get targeted error messages.
  • Tooling & docs — Vite 8 upgrade cuts build time by 60% and bundle size by 5%, reorganized docs into guides and references, updated README
  • Application hardening — tighter CORS defaults, supply chain hardening, automated vulnerability scanning, least-privilege CI permissions, and a new security policy for reporting vulnerabilities
  • Proxy server — previously untestable parts of the proxy server now have 170+ tests (up from 56), making future changes safer and more reliable

HTTPS Configuration

Previous versions had a bug where the Docker entrypoint ignored custom config directory paths, which could cause your HTTPS settings to be silently skipped. While fixing this, we also discovered that when HTTPS was enabled but certificate generation or discovery failed, the server would silently fall back to HTTP instead of reporting the problem. The server now exits with a clear error in this scenario. If you were unknowingly relying on this fallback behavior, ensure your certificates are in place before upgrading or explicitly disable HTTPS. See the HTTPS Connections documentation for details.

New Contributors

Welcome and thank you to our first-time contributor!

All Changes

Full Changelog: v3.0.0...v3.0.1

Release 3.0.0

05 Mar 02:35
5485ec6

Choose a tag to compare

Graph Explorer 3.0 is here! This release brings one of the most requested features — the ability to visualize your graph database schema — along with a fresh navigation experience and a handful of quality-of-life improvements.

If you're upgrading from a previous version, all your existing connections, preferences, and configuration data will carry over unchanged.

Schema Explorer

You can now see the shape of your graph at a glance. The new Schema Explorer renders your vertex types, edge types, and their connections as an interactive schema graph. Drill into any type from the sidebar to see property details and data types. Edge connection discovery maps out how your types relate, giving you a bird's-eye view of your entire graph structure.

The schema is built by sampling your graph data, so it reflects what Graph Explorer has seen so far and may not capture every type or property in your database.

Screenshot of the Schema Explorer UI

Redesigned Navigation

Getting around Graph Explorer just got easier. The navigation bar has been rebuilt as a clean, static top bar for moving between the Graph Explorer, Data Explorer, and Schema Explorer. Sidebar tabs have been refreshed to match the new look.

Screenshot of the Graph Explorer UI

Data Explorer Improvements

The Data Explorer now includes a vertex type switcher for faster browsing across types and a new export button to download data as CSV or JSON (thanks @dwrth!).

Screenshot of the Data Explorer UI

Other Improvements

  • Rewritten RDF prefix generation and replacement logic
  • Standardized terminology across Gremlin, openCypher, and SPARQL
  • Very large and very small numbers now display using scientific notation
  • Keyword search labels are clearer and more descriptive

New Contributors

Welcome and thank you to our first-time contributors! 🎉

All Changes

Read more

Release 2.5.2

21 Jan 00:09
a98fcff

Choose a tag to compare

This release bumps the Node & PNPM versions and cleans up the Docker image.

All Changes

Full Changelog: v2.5.1...v2.5.2

Release 2.5.1

07 Jan 21:11
5617b9c

Choose a tag to compare

This release includes a fix for a regression that caused neighbor expansion in SPARQL databases to perform poorly.

All Changes

Full Changelog: v2.5.0...v2.5.1

Release 2.5.0

11 Dec 20:43
7260156

Choose a tag to compare

This release focuses on improving the graph exploration experience with access to the raw response, enhanced node
interactions, and performance optimizations.

New Features

  • Raw JSON Response Viewer: View query results as formatted JSON with syntax highlighting and copy
    functionality for better debugging
  • Enhanced Node Expansion: Expand single or multiple selected nodes simultaneously through an improved context
    menu
  • Graph View Improvements: Added toggle buttons to the empty state and updated the re-layout button icon for
    clarity

Improvements

  • Better Context Menu: Reorganized options with new abilities to center/zoom to selected items and remove all
    selected items
  • Performance: Faster app startup by lazy-loading Cytoscape and other heavy dependencies (38% reduction in
    initial bundle size)
  • UI Polish: Updated table and notification styling, plus fixed node stacking issues in graph rendering
  • Stability: Resolved race conditions that caused inconsistent behavior during app initialization

All Changes

Full Changelog: v2.4.1...v2.5.0

Release v2.4.1

18 Nov 22:08
fced570

Choose a tag to compare

This release includes several important bug fixes and improvements, notably:

  • Added ability to manually refresh node or edge data from UI
  • Updated graph data to mirror the most recent data from searches and queries
  • Updated handling of multi-label nodes when patching the schema
  • Fixed auto-open details panel behavior when selecting entities
  • Fixed representation of default values in node & edge styles
  • Fixed several layout issues around long labels

All Changes

Full Changelog: v2.4.0...v2.4.1

Release v2.4.0

22 Oct 21:23
41daf44

Choose a tag to compare

This release introduces support for SPARQL queries within the query editor. Now, all three query engines are supported: Gremlin, openCypher, and SPARQL. This does not mean we are done with the query editor. We have many exciting ideas being considered for future releases.

SPARQL Query Support

  • Support for SELECT, ASK, DESCRIBE, and CONSTRUCT queries
  • DESCRIBE and CONSTRUCT queries will result in fully materialized vertex and edge results
  • SELECT and ASK queries will result in raw statements, but do not materialize results as vertices or edges
  • Support for RDF resources without a defined rdf:type
  • Updated display name defaults to use rdfs:label if it is available

Other Notable Changes

  • Added support for vertices that have no label in openCypher
  • Hide properties that don't have a value for the given vertex or edge
  • Added confirmation dialog when deleting a connection (thanks @dwrth)
  • Added ability to horizontally scroll toolbars if space is limited (thanks @Ansh2004P)
  • Added zoom to fit toolbar button (thanks @cnaples79)
  • Updated the strings used to represent no value, no type, and empty value to be more clear
  • Updated handling of neighbor counts when neighbors have more than one type or label
  • Updated handling of date values, specifically in openCypher connections
  • Updated behavior of auto open details panel when a node is selected
  • Fixed many bugs

All Changes

New Contributors

Full Changelog: v2.3.1...v2.4.0

Release 2.3.1

04 Sep 15:54
697b262

Choose a tag to compare

This release resolves a few important issues from the previous release.

All changes

Full Changelog: v2.3.0...v2.3.1