This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hop-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d8a2e086ce Website updated to ffb962c
d8a2e086ce is described below
commit d8a2e086cefd9b2d0c4de8361d097e5a1bde0744
Author: jenkins <[email protected]>
AuthorDate: Thu Oct 22 13:01:19 2026 +0000
Website updated to ffb962c
---
manual/next/hop-tools/hop-lint.html | 8 +++++++-
manual/next/linting/lint-rules.html | 25 +++++++++++++++++++++++
manual/next/technology/graph-databases/index.html | 4 ++--
manual/next/workflow/actions/runlinter.html | 2 +-
4 files changed, 35 insertions(+), 4 deletions(-)
diff --git a/manual/next/hop-tools/hop-lint.html
b/manual/next/hop-tools/hop-lint.html
index bd55e272a9..f097e2de6b 100644
--- a/manual/next/hop-tools/hop-lint.html
+++ b/manual/next/hop-tools/hop-lint.html
@@ -2989,6 +2989,9 @@ hop lint --list-rules <span
class="hljs-comment"># show the effe
hop lint --<span class="hljs-built_in">help</span> <span
class="hljs-comment"># full option list</span></code></pre>
</div>
</div>
+<div class="paragraph">
+<p>Relative paths, for the target and for options such as
<code>--output</code>, <code>--config</code> and <code>--baseline</code>, are
relative to the folder the command is run from.</p>
+</div>
</div>
</div>
<div class="sect1">
@@ -3036,7 +3039,8 @@ A project chosen with <code>-j</code> or <code>-e</code>
applies whatever is lin
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>--fail-on <severity></code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Exit with
1 when a finding reaches this severity. Default <code>ERROR</code>.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Exit with
1 when a finding reaches this severity: <code>ERROR</code> (the default),
<code>WARNING</code>, <code>INFO</code> or <code>NONE</code>.
+Any other value is refused.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>--max-warnings <n></code></p></td>
@@ -3180,6 +3184,8 @@ Counts are kept, so a second orphaned transform in a file
that already had one i
<div class="paragraph">
<p>This writes a <code>pre-commit</code> hook into the current
repository’s <code>.git/hooks</code>.
The hook lints the staged Hop files and blocks the commit when they fail.
+It lints the staged version of each file, which is what the commit holds, not
the one on disk, and it includes files renamed with <code>git mv</code>.
+Set <code>HOP_LINT_FAIL_ON</code> to change the threshold the hook fails on,
for example <code>HOP_LINT_FAIL_ON=WARNING</code>.
It is a copy, so run <code>hop lint --install-hook</code> again after
upgrading Hop to pick up changes to it.</p>
</div>
<div class="paragraph">
diff --git a/manual/next/linting/lint-rules.html
b/manual/next/linting/lint-rules.html
index e36f164157..5cbd9e2189 100644
--- a/manual/next/linting/lint-rules.html
+++ b/manual/next/linting/lint-rules.html
@@ -3103,6 +3103,12 @@ Scope such a rule with <code>appliesTo</code>, naming
the metadata key — the f
</tr>
</tbody>
</table>
+<div class="paragraph">
+<p><code>conditionValue</code> is used as written: variables are not resolved
in it.
+A value the condition cannot use, such as <code>abc</code> or <code>3,0</code>
for <code>MAX_VALUE</code>, or <code>[a-</code> for
<code>MATCHES_PATTERN</code>, would make the rule report nothing at all.
+The rule editor refuses it, and a rule loaded from <code>hop-lint.yml</code>
or a rule pack gets a warning in the log that names the rule and the problem.
+The same goes for a condition that does not fit one of the fields the linter
provides, such as <code>NOT_NULL</code> on <code>transformCount</code>.</p>
+</div>
</div>
</div>
<div class="sect1">
@@ -3503,9 +3509,28 @@ The rule manager lists each rule’s tags in its
<strong>Tags</strong> colum
<td class="tableblock halign-left valign-top"><p
class="tableblock">WARNING</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Every
remark from Hop’s own transform and action checks</p></td>
</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>SYSTEM-001</code></p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock">ERROR</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A
pipeline, workflow or metadata file that could not be loaded, so nothing was
checked against it</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>SYSTEM-002</code></p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock">ERROR</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A lint run
that stopped before it finished</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>SYSTEM-003</code></p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock">ERROR</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A metadata
file, such as a connection, that could not be read</p></td>
+</tr>
</tbody>
</table>
<div class="paragraph">
+<p>The <code>SYSTEM</code> rules are of <code>type: system</code>: like a
native rule they check nothing, and say how the linter reports a file it could
not read or a run it could not finish.
+A project can change their severity, or switch one off, in its
<code>hop-lint.yml</code> like any other rule.</p>
+</div>
+<div class="paragraph">
<p><code>TRANS-002</code> and <code>WORKFLOW-002</code> report on the
transform or action itself, so the finding names it and the canvas can point at
it.
The only element in a file is not an orphan — there is nothing for it to be
disconnected from — and neither is one whose hops are all disabled: it has
hops, and whether a disabled hop is a problem is what <code>STRUCT-003</code>
asks.</p>
</div>
diff --git a/manual/next/technology/graph-databases/index.html
b/manual/next/technology/graph-databases/index.html
index f775eda059..692e8305fa 100644
--- a/manual/next/technology/graph-databases/index.html
+++ b/manual/next/technology/graph-databases/index.html
@@ -3214,11 +3214,11 @@ Memgraph’s <code>similarity</code> column is the
absolute value of 1 - dis
</div>
</div>
<div class="sect1">
-<h2 id="_upgrading_from_hop_2_20_or_earlier"><a class="link"
href="#_upgrading_from_hop_2_20_or_earlier">Upgrading from Hop 2.20 or
earlier</a></h2>
+<h2 id="_upgrading_from_hop_2_19_or_earlier"><a class="link"
href="#_upgrading_from_hop_2_19_or_earlier">Upgrading from Hop 2.19 or
earlier</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>The graph functionality of Hop used to be Neo4j specific.
-From Hop 2.21 on it works with every graph database above. Existing projects
keep working without changes:</p>
+From Hop 2.20 on it works with every graph database above. Existing projects
keep working without changes:</p>
</div>
<div class="ulist">
<ul>
diff --git a/manual/next/workflow/actions/runlinter.html
b/manual/next/workflow/actions/runlinter.html
index a8d0e13441..a14b215016 100644
--- a/manual/next/workflow/actions/runlinter.html
+++ b/manual/next/workflow/actions/runlinter.html
@@ -3024,7 +3024,7 @@ It does not change whether the action fails, nor the
counts in the variables. De
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Fail
on</p></td>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>--fail-on</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Fail when
a finding reaches this severity: <code>Error</code> (the default),
<code>Warning</code> or <code>None</code>.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Fail when
a finding reaches this severity: <code>Error</code> (the default),
<code>Warning</code>, <code>Info</code> or <code>None</code>.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Max
warnings</p></td>
