Skip to content

docs: update README.md for 26.3.1 release - #3586

Merged
robfrank merged 4 commits into
mainfrom
imp/update-reasme
Mar 6, 2026
Merged

robfrank merged 4 commits into
mainfrom
imp/update-reasme

Conversation

@robfrank

@robfrank robfrank commented Mar 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add Geospatial model to the supported models list
  • Add key capabilities section highlighting major 26.3.1 features: 73 graph algorithms, parallel query execution, materialized views, MCP server, AI assistant, geospatial indexing, TimeSeries enhancements, hash indexes
  • Add MCP Server as a usage mode under "can be used as"
  • Add base release variant to the releases section
  • Update Java 17 version references from 25.5.1 to 26.3.1
  • Fix typo in full variant description ("of including" → "including")
  • Enhance Time Series model description with InfluxDB/Prometheus/PromQL details

Test plan

  • Verify README renders correctly on GitHub
  • Confirm all documentation links are valid

🤖 Generated with Claude Code

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>
@mergify

mergify Bot commented Mar 6, 2026 •

Copy link
Copy Markdown
Contributor

🧪 CI Insights

Here's what we observed from your CI run for c95b894.

🟢 All jobs passed!

But CI Insights is watching 👀

@claude

claude Bot commented Mar 6, 2026

Copy link
Copy Markdown

Review of PR #3586: README.md update for 26.3.1

Good 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 stale

The introductory sentence for the releases section was not updated:

There are three variants of (about monthly) releases:

But the PR adds a fourth (base), so this should read four variants.

base variant description is incomplete

The existing variants describe themselves by what they include/exclude:

  • minimal — excludes gremlin, redisw, mongodbw, graphql
  • headless — excludes the above plus studio

The new base entry just says "core engine only, minimal footprint" without listing which modules are included or excluded. For consistency and user clarity, it should follow the same pattern as the others (e.g., "excludes gremlin, redisw, mongodbw, graphql, studio, postgresw, bolt, ...").

URL inconsistency (pre-existing, but compounded)

The README mixes two URL formats for docs anchors. Some links use docs.arcadedb.com#anchor and others use docs.arcadedb.com/#anchor. The new entries introduced here are also inconsistent with each other:

  • [Geospatial] → https://docs.arcadedb.com/#geospatial-model ✓ (with slash)
  • [Model Context Protocol] → https://docs.arcadedb.com#mcp ✗ (no slash)
  • [MCP Server] in usage modes → https://docs.arcadedb.com#mcp ✗ (no slash)

Not a blocker, but normalizing new additions to the /# form would be cleaner.

TimeSeries description is duplicated

The Time Series model entry in the models list now says:

(with InfluxDB Line Protocol, Prometheus remote_write/read, and PromQL support)

And the key capabilities section also says:

Columnar storage with Gorilla/Delta-of-Delta compression, InfluxDB/Prometheus ingestion, PromQL queries, Grafana integration

Minor redundancy — not a blocker, but the two descriptions could be made complementary rather than overlapping.

Verify the "73 Graph Algorithms" number

The specific count 73 in the capabilities section will look outdated or inaccurate if it drifts. It might be worth either confirming this is correct for 26.3.1 or using a softer phrasing (e.g., "70+ built-in graph algorithms") that doesn't require updating every release.

Test plan items are unchecked

Both items in the PR description test plan are still unchecked ([ ]). Please verify the docs links resolve correctly before merging — especially #geospatial-model and #mcp which are new anchors.


Summary: The stale "three variants" count and the vague base description are the only concrete issues that need fixing. The rest are suggestions.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 README.md file to reflect the latest features and capabilities introduced in the 26.3.1 release of ArcadeDB. The changes aim to provide a more comprehensive and up-to-date overview of the database's supported models, key functionalities, usage modes, and release variants, ensuring that users have accurate information about the current state of the project.

Highlights

  • New Model Support: The 'Geospatial' model has been added to the list of supported data models in ArcadeDB.
  • Enhanced Time Series Description: The description for the 'Time Series' model now includes details about InfluxDB Line Protocol, Prometheus remote_write/read, and PromQL support.
  • Key Capabilities Section: A new section highlighting ArcadeDB's key capabilities has been introduced, covering features like 73 graph algorithms, parallel query execution, materialized views, MCP Server, AI Assistant, geospatial indexing, TimeSeries enhancements, and hash indexes.
  • New Usage Mode: ArcadeDB can now be used 'By AI assistants via the built-in MCP Server', reflecting its integration capabilities.
  • New Release Variant: A 'base' release variant, representing the core engine only with a minimal footprint, has been added to the release options.
  • Typo Correction: A minor typo in the description of the 'full' release variant was corrected from 'of including' to 'including'.
  • Version Update: References to Java 17 versions for Maven dependency and Docker images have been updated from 25.5.1 to 26.3.1.

🧠 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
  • README.md
    • Added 'Geospatial' model to the list of supported models.
    • Updated the description for the 'Time Series' model to include InfluxDB/Prometheus/PromQL support.
    • Introduced a new 'ArcadeDB key capabilities' section detailing various features.
    • Added 'By AI assistants via the built-in MCP Server' as a new usage mode.
    • Included the 'base' release variant and corrected a typo in the 'full' variant description.
    • Updated Java 17 version references for Maven dependency and Docker pull command from 25.5.1 to 26.3.1.
Activity
  • The pull request was created by robfrank to update the README.md for the 26.3.1 release.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

robfrank and others added 2 commits March 6, 2026 15:14
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>
@claude

claude Bot commented Mar 6, 2026

Copy link
Copy Markdown

PR #3586 Review: README.md update for 26.3.1

Good 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 updated

The introductory sentence was not updated when the new base variant was added:

There are three variants of (about monthly) releases:

With base now listed, this should read four variants.


base variant description is incomplete

The existing variants describe what they include/exclude:

  • minimal — excludes gremlin, redisw, mongodbw, graphql
  • headless — excludes the above plus studio

The new entry just says "core engine only, minimal footprint", which is inconsistent. Per package/src/main/assembly/base.xml and README-BUILDER.md, the base is engine + server + network only. It should follow the same pattern, e.g.:

base - core engine, server and network only, no optional modules


Hardcoded version in curl example will go stale immediately

The custom builder example hardcodes 26.3.1:

curl -fsSL https://github.com/ArcadeData/arcadedb/releases/download/26.3.1/arcadedb-builder.sh | \
  bash -s -- --version=26.3.1 --modules=gremlin,studio

Note also that README-BUILDER.md (the canonical builder docs) still references 26.1.1 in its examples — there is already a version drift. In the README, consider either using a placeholder (e.g., <VERSION>) or pointing readers to README-BUILDER.md directly instead of duplicating the example.


Naming inconsistency: "Time Series" vs "TimeSeries"

The models list uses "Time Series" (two words), but the new key capabilities section uses "TimeSeries" (CamelCase). Pick one and be consistent:

- [Time Series](...) (with InfluxDB ...)           ← two words
...
- **TimeSeries** — Columnar storage ...             ← one word

URL format inconsistency in new entries

The README mixes docs.arcadedb.com#anchor and docs.arcadedb.com/#anchor. The two new links introduced in this PR add to the inconsistency:

  • [Geospatial](https://docs.arcadedb.com/#geospatial-model) — has the slash ✓
  • [Model Context Protocol](https://docs.arcadedb.com#mcp) — missing the slash
  • [MCP Server](https://docs.arcadedb.com#mcp) — missing the slash

Consider normalizing all new additions to the /#anchor form.


TimeSeries details are duplicated

InfluxDB/Prometheus/PromQL appear in both places now:

  1. Model list: "(with InfluxDB Line Protocol, Prometheus remote_write/read, and PromQL support)"
  2. Key capabilities: "InfluxDB/Prometheus ingestion, PromQL queries, Grafana integration"

The entries are slightly different (the second adds Grafana), which may confuse readers. Either consolidate to one canonical location or make them clearly complementary (e.g., the model list entry just links to the docs, and the capabilities section gives the detail).


Summary: The content additions are accurate and welcome. The main blocking issue is the stale "three variants" count. The other points are consistency improvements.

@robfrank

robfrank commented Mar 6, 2026

Copy link
Copy Markdown
Collaborator Author

Addressed the review feedback in b658f86:

  • "three variants" → "four" — Fixed the stale count now that base was added.
  • base description — Expanded to list all excluded optional modules (console, gremlin, studio, redisw, mongodbw, postgresw, grpcw, graphql, metrics), matching the pattern used by minimal and headless.
  • URL normalization — New doc links (#mcp, #timeseries-model) updated to use the /#anchor form for consistency with existing links like /#studio, /#docker, /#geospatial-model.
  • Algorithm count — Changed from "73" to "70+" to avoid the number going stale across releases.
  • TimeSeries duplication — Left as-is. The two mentions serve different purposes: the model list highlights protocol compatibility (InfluxDB, Prometheus, PromQL), while the capabilities section describes internals (columnar storage, compression, Grafana integration). They're complementary rather than redundant.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread README.md
- [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)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
- [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)

Comment thread README.md
- **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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
- **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

Comment thread README.md
- 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)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
- 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)

@claude

claude Bot commented Mar 6, 2026

Copy link
Copy Markdown

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>
@claude

claude Bot commented Mar 6, 2026

Copy link
Copy Markdown

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 naming

The models list correctly uses Time Series (two words, matching the model's canonical name), but the key capabilities section uses TimeSeries (CamelCase):

- [Time Series](...) (with InfluxDB Line Protocol, ...)     <- model list, two words (correct)
- **TimeSeries** -- Columnar storage with Gorilla/...       <- capabilities section, one word (inconsistent)

Suggest changing TimeSeries to Time Series in the capabilities section.

Still open: hardcoded version in curl example

The 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,studio

Minor: curl | bash security note

The 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.

@codacy-production

codacy-production Bot commented Mar 6, 2026 •

Copy link
Copy Markdown

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
✅ -9.87% ✅ ∅
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (0db7907) 103661 77401 74.67%
Head commit (6da5b5a) 134220 (+30559) 86976 (+9575) 64.80% (-9.87%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#3586) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

@robfrank
robfrank merged commit 2768254 into main Mar 6, 2026
20 of 23 checks passed
@codecov

codecov Bot commented Mar 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.80%. Comparing base (0db7907) to head (c95b894).
⚠️ Report is 1 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

robfrank added a commit that referenced this pull request May 12, 2026
tae898 pushed a commit to humemai/arcadedb-embedded-python that referenced this pull request Jun 28, 2026
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)
  
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=pg&package-manager=npm\_and\_yarn&previous-version=8.17.2&new-version=8.18.0)](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)
tae898 pushed a commit to humemai/arcadedb-embedded-python that referenced this pull request Jun 28, 2026
@lvca
lvca deleted the imp/update-reasme branch July 3, 2026 20:19
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