Repository navigation
docs: update README.md for 26.3.1 release - #3586
Conversation
Add new features from 26.3.1: geospatial model, key capabilities section (graph algorithms, parallel queries, materialized views, MCP server, AI assistant, hash indexes), MCP usage mode, base release variant, and update Java 17 version references to 26.3.1. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
🧪 CI InsightsHere's what we observed from your CI run for c95b894. 🟢 All jobs passed!But CI Insights is watching 👀 |
Review of PR #3586: README.md update for 26.3.1Good additions overall — the new "key capabilities" section and Geospatial model entry make the README more informative. A few issues worth addressing before merging: Bug: Release variant count is staleThe introductory sentence for the releases section was not updated:
But the PR adds a fourth (
|
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Add a brief section after the release variants describing the modular distribution builder with a one-liner example and list of available optional modules. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix stale "three variants" count to "four" - Expand `base` variant description to list excluded modules - Normalize new doc links to `/#anchor` form for consistency - Use "70+" for graph algorithm count to avoid drift Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
PR #3586 Review: README.md update for 26.3.1Good additions overall — the new "key capabilities" section, Geospatial model entry, and MCP usage mode meaningfully improve the README. Here are the issues worth addressing before merging: Bug: Release variant count not updatedThe introductory sentence was not updated when the new
With
|
|
Addressed the review feedback in b658f86:
|
There was a problem hiding this comment.
Code Review
This pull request updates the README.md file to reflect the features and changes for the 26.3.1 release. The changes include adding new models and capabilities, updating version numbers, and fixing a typo. My review focuses on ensuring consistency in the documentation. I've noticed some inconsistencies in the formatting of documentation links and have provided suggestions to address them.
Note: Security Review has been skipped due to the limited scope of the PR.
| - [Key/Value](https://docs.arcadedb.com#keyvalue-model) (compatible with the Redis driver) | ||
| - [Search Engine](https://docs.arcadedb.com/#searchengine-model) | ||
| - [Time Series](https://docs.arcadedb.com#timeseries-model) | ||
| - [Time Series](https://docs.arcadedb.com/#timeseries-model) (with InfluxDB Line Protocol, Prometheus remote_write/read, and PromQL support) |
There was a problem hiding this comment.
There's an inconsistency in the URL formatting for documentation links. Some links include a trailing slash before the anchor (e.g., for Search Engine and Geospatial), while others do not. For consistency, it would be best to add a slash here.
| - [Time Series](https://docs.arcadedb.com/#timeseries-model) (with InfluxDB Line Protocol, Prometheus remote_write/read, and PromQL support) | |
| - [Time Series](https://docs.arcadedb.com/#timeseries-model) (with InfluxDB Line Protocol, Prometheus remote_write/read, and PromQL support) |
| - **70+ Built-in Graph Algorithms** — Pathfinding, centrality, community detection, link prediction, graph embeddings, and more — all available out of the box | ||
| - **Parallel Query Execution** — SQL queries leverage multiple CPU cores for faster execution on large datasets | ||
| - **Materialized Views** — Pre-computed query results stored and automatically maintained | ||
| - **MCP Server** — Built-in [Model Context Protocol](https://docs.arcadedb.com/#mcp) server for AI assistant and LLM integration |
There was a problem hiding this comment.
To maintain consistency with other documentation links in this file (like for Studio and Docker), please add a trailing slash before the anchor in this URL.
| - **MCP Server** — Built-in [Model Context Protocol](https://docs.arcadedb.com/#mcp) server for AI assistant and LLM integration | |
| - **MCP Server** — Built-in [Model Context Protocol](https://docs.arcadedb.com/#mcp) server for AI assistant and LLM integration |
| - Remotely by using a [Postgres driver](https://docs.arcadedb.com#postgres-driver) (ArcadeDB implements Postgres Wire protocol) | ||
| - Remotely by using a [Redis driver](https://docs.arcadedb.com#redis-query-language) (only a subset of the operations are implemented) | ||
| - Remotely by using a [MongoDB driver](https://docs.arcadedb.com#mongodb-query-language) (only a subset of the operations are implemented) | ||
| - By AI assistants via the built-in [MCP Server](https://docs.arcadedb.com/#mcp) (Model Context Protocol) |
There was a problem hiding this comment.
This link to the MCP Server documentation is also missing the trailing slash before the anchor. Adding it will improve consistency with other links in the README.
| - By AI assistants via the built-in [MCP Server](https://docs.arcadedb.com/#mcp) (Model Context Protocol) | |
| - By AI assistants via the built-in [MCP Server](https://docs.arcadedb.com/#mcp) (Model Context Protocol) |
Review of PR #3586 (current state)The third commit addressed the prior review feedback well: variant count, base description, URL normalization, and graph algorithm phrasing are all fixed. Two small items remain: 1. Hardcoded version in curl example The custom builder snippet hardcodes 26.3.1 in two places, which will go stale with the next release. Consider using a placeholder like VERSION and directing readers to the releases page to find the current version — consistent with how the rest of the README handles version references. 2. TimeSeries vs Time Series naming inconsistency The models list uses Time Series (two words), but the key capabilities section uses TimeSeries (one word/CamelCase). These should be consistent — Time Series (two words, matching the model name) is the right form. Everything else looks good. The new content is accurate and the README is meaningfully improved with the Geospatial model, key capabilities section, MCP usage mode, and base variant. |
List the seven self-contained demo projects (recommendation engine, knowledge graphs, graph RAG, fraud detection, real-time analytics, social network analytics, supply chain) with their key ArcadeDB features. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Review of PR #3586 (follow-up)The previous feedback has been well-addressed. Here is what I observe in the current diff: Still open: TimeSeries vs Time Series namingThe models list correctly uses Time Series (two words, matching the model's canonical name), but the key capabilities section uses TimeSeries (CamelCase): Suggest changing TimeSeries to Time Series in the capabilities section. Still open: hardcoded version in curl exampleThe version 26.3.1 appears twice in the builder snippet and will go stale with the next release. Using a variable would make it easier to update: # Replace VERSION with the latest from https://github.com/ArcadeData/arcadedb/releases
VERSION=26.3.1
curl -fsSL https://github.com/ArcadeData/arcadedb/releases/download/VERSION/arcadedb-builder.sh | bash -s -- --version=VERSION --modules=gremlin,studioMinor: curl | bash security noteThe script-piping pattern is common but security-conscious docs often include a brief note to inspect the script before running (e.g., a comment linking to the script source). Optional, but aligns with best practices for docs that recommend executing remote scripts. Overall: The PR is a meaningful improvement to the README -- Geospatial model, key capabilities section, MCP usage mode, base variant, and use cases section are all welcome additions. The two open items (naming consistency, hardcoded version) are minor but worth a quick fix before merging. |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3586 +/- ##
==========================================
+ Coverage 65.69% 65.80% +0.10%
==========================================
Files 1514 1514
Lines 103661 103661
Branches 21454 21454
==========================================
+ Hits 68100 68213 +113
+ Misses 26288 26193 -95
+ Partials 9273 9255 -18 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
(cherry picked from commit 2768254)
Bumps [pg](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg) from 8.17.2 to 8.18.0. Changelog *Sourced from [pg's changelog](https://github.com/brianc/node-postgres/blob/master/CHANGELOG.md).* > pg@8.18.0 > --------- > > * [Return the client instance](https://redirect.github.com/brianc/node-postgres/pull/3564) as the result of calling `connect` (previously it was `void`). > > pg@8.17.0 > --------- > > * Throw correct error if database URL parsing [fails](https://redirect.github.com/brianc/node-postgres/issues/3513). > > pg@8.16.0 > --------- > > * Add support for [min connection pool size](https://redirect.github.com/brianc/node-postgres/pull/3438). > > pg@8.15.0 > --------- > > * Add support for [esm](https://redirect.github.com/brianc/node-postgres/pull/3423) importing. CommonJS importing is still also supported. > > pg@8.14.0 > --------- > > * Add support from SCRAM-SAH-256-PLUS i.e. [channel binding](https://redirect.github.com/brianc/node-postgres/pull/3356). > > pg@8.13.0 > --------- > > * Add ability to specify query timeout on [per-query basis](https://redirect.github.com/brianc/node-postgres/pull/3074). > > pg@8.12.0 > --------- > > * Add `queryMode` config option to [force use of the extended query protocol](https://redirect.github.com/brianc/node-postgres/pull/3214) on queries without any parameters. > > pg-pool@8.10.0 > -------------- > > * Emit `release` event when client is returned to [the pool](https://redirect.github.com/brianc/node-postgres/pull/2845). > > pg@8.9.0 > -------- > > * Add support for [stream factory](https://redirect.github.com/brianc/node-postgres/pull/2898). > * [Better errors](https://redirect.github.com/brianc/node-postgres/pull/2901) for SASL authentication. > * [Use native crypto module](https://redirect.github.com/brianc/node-postgres/pull/2815) for SASL authentication. > > pg@8.8.0 > -------- > > * Bump minimum required version of [native bindings](https://redirect.github.com/brianc/node-postgres/pull/2787). > * Catch previously uncatchable errors thrown in [`pool.query`](https://redirect.github.com/brianc/node-postgres/pull/2569). > * Prevent the pool from blocking the event loop if all clients are [idle](https://redirect.github.com/brianc/node-postgres/pull/2721) (and `allowExitOnIdle` is enabled). > * Support `lock_timeout` in [client config](https://redirect.github.com/brianc/node-postgres/pull/2779). > * Fix errors thrown in callbacks from [interfering with cleanup](https://redirect.github.com/brianc/node-postgres/pull/2753). > > ### pg-pool@3.5.0 > > * Add connection [lifetime limit](https://redirect.github.com/brianc/node-postgres/pull/2698) config option. ... (truncated) Commits * [`fc4de3c`](brianc/node-postgres@fc4de3c) Publish * [`0d1541d`](brianc/node-postgres@0d1541d) Always check if activeQuery is null before using it ([ArcadeData#3586](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3586)) * [`57e93b5`](brianc/node-postgres@57e93b5) Return the client instance in the `connect()` method ([ArcadeData#3564](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3564)) * See full diff in [compare view](https://github.com/brianc/node-postgres/commits/pg@8.18.0/packages/pg) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Summary
25.5.1to26.3.1fullvariant description ("of including" → "including")Test plan
🤖 Generated with Claude Code