This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a change to branch gremlin-mcp
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
discard 7d0c33c01c README updates on gremlin-mcp
discard 7b2d11e28d Docs about unexpected mutations by gremlin-mcp
discard 9609b0eef6 Cleaned up around denylist and better documented enum
discard 846bdb96b6 Minor doc updates
discard 45de882e7c Added upgrade docs for gremlin-mcp
discard 2ed68a5cb5 Added point about testing gremlin-mcp to dev docs
discard 5632cc34d4 Moved gremlin-mcp to root
discard 60a5e72abb Cleaned up LICENSE on gremlin-mcp
discard f511c2c6ce Update docs for Javascript dev environment setup
discard cf6f7843ae Use centralized node version for gremlint
discard b070899365 Hooked up build via maven and ran eslint in process
discard 4227c16ee2 Restructured gremlin-mcp to match TinkerPop standards under
Maven
discard 843afa578d Bumped back to SNAPSHOT
discard 5b8f21c7c2 Added warning about global traversals to docs
discard 212ffcece6 Added asciidoc for gremlin-mcp
discard 0f0b66baa0 TinkerPop prefers edges to relationships in its naming
discard c16716d820 Adjusted packaging for TinkerPop official use
discard 4343cbc741 TinkerPop prefers the use of the term vertex over node.
discard b625b3e876 Port gremlin-mcp from kpritam/gremlin-mcp
add 8dc2e26b44 Fixed bug where InlineFilterStrategy could add extra has()
new 1808c814fc Port gremlin-mcp from kpritam/gremlin-mcp
new a3eaf4f479 TinkerPop prefers the use of the term vertex over node.
new 7596c50588 Adjusted packaging for TinkerPop official use
new 8607ef90b3 TinkerPop prefers edges to relationships in its naming
new 7990d8368e Added asciidoc for gremlin-mcp
new 6c5a5e2985 Bumped back to SNAPSHOT
new 966cb46bb8 Restructured gremlin-mcp to match TinkerPop standards under
Maven
new e50775bb7c Cleaned up around denylist and better documented enum
new eda3b45aef Remove import tool from gremlin-mcp.
new f9a1cec15b Improved tool definitions
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (7d0c33c01c)
\
N -- N -- N refs/heads/gremlin-mcp (f9a1cec15b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 10 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
CHANGELOG.asciidoc | 1 +
docs/src/reference/gremlin-applications.asciidoc | 16 +-
.../optimization/InlineFilterStrategy.java | 7 +-
gremlin-mcp/src/main/javascript/README.md | 26 +--
gremlin-mcp/src/main/javascript/src/constants.ts | 1 -
gremlin-mcp/src/main/javascript/src/errors.ts | 1 -
.../javascript/src/gremlin/models/import-export.ts | 47 +---
.../src/main/javascript/src/handlers/tools.ts | 127 ++++-------
.../main/javascript/src/utils/data-operations.ts | 246 +--------------------
.../tests/integration/mcp-integration.test.ts | 1 -
10 files changed, 73 insertions(+), 400 deletions(-)