This is an automated email from the ASF dual-hosted git repository.

colegreer pushed a commit to branch 3.8-dev
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git


The following commit(s) were added to refs/heads/3.8-dev by this push:
     new 876827c849 Various upgrade doc fixes for 3.8.0. (#3279)
876827c849 is described below

commit 876827c849509db6900998c9775976df7021d81b
Author: andreachild <[email protected]>
AuthorDate: Thu Nov 13 13:37:50 2025 -0800

    Various upgrade doc fixes for 3.8.0. (#3279)
---
 docs/src/upgrade/release-3.8.0.asciidoc | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/src/upgrade/release-3.8.0.asciidoc 
b/docs/src/upgrade/release-3.8.0.asciidoc
index 9ff92294d6..dbdcb6b1ca 100644
--- a/docs/src/upgrade/release-3.8.0.asciidoc
+++ b/docs/src/upgrade/release-3.8.0.asciidoc
@@ -30,7 +30,7 @@ changes primarily focus on standardizing scoping behavior 
(local vs global), sim
 related steps behave more consistently and interoperably with one another.
 
 New steps and predicates have been added for type conversion and type testing, 
providing better control over graphs with
-mixed-type properties. Additionally, this release adds support for [Model 
Context Protocol (MCP)](https://modelcontextprotocol.io/)
+mixed-type properties. Additionally, this release adds support for 
link:https://modelcontextprotocol.io[Model Context Protocol (MCP)]
 with the initial version of `gremlin-mcp` server.
 
 The following table summarizes the impact level of each change, which can help 
form a guide by which to develop an
@@ -308,6 +308,7 @@ or 'd') as Double by default. Users who need `BigDecimal` 
precision can still us
 
 ==== Modified Step Behavior
 
+[[datediff-step-returns-milliseconds]]
 ===== dateDiff() Step Returns Milliseconds
 
 The `dateDiff()` step has been changed to return milliseconds instead of 
seconds for consistency with the `asDate()` 
@@ -489,8 +490,6 @@ should be moved out of the `repeat()` step.
 have led to unexpected results since `cap()` isn't "repeat-aware". Because 
`cap()` is a `SupplyingBarrier` that reduces
 the number of traversers to one, its use inside `repeat()` is limited.
 
-See: link:https://issues.apache.org/jira/browse/TINKERPOP-3195[TINKERPOP-3195]
-
 `inject()` inside `repeat()` is now also disallowed by the 
`StandardVerificationStrategy`. The usefulness of `inject()`
 inside `repeat()` is questionable as the injections are exhausted after one 
iteration. Consider the following examples,
 noting that the examples for version 3.7.4 demonstrate the effect of 
`RepeatUnrollStrategy` on `inject()` semantics,
@@ -543,6 +542,8 @@ gremlin> 
g.inject('x').repeat(union(constant(['a','b']).limit(1).unfold(),identi
 ==>x
 ----
 
+See: link:https://issues.apache.org/jira/browse/TINKERPOP-3195[TINKERPOP-3195]
+
 [[stricter-repeatunrollstrategy]]
 ====== Stricter RepeatUnrollStrategy
 

Reply via email to