BP-2603: Release notes (2026-05-26)#291
Conversation
…atic node selection
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughThis PR updates documentation for BloodHound v9.2.0 release, introducing OpenGraph reserved prefix validation rules ( ChangesBloodHound v9.2.0 Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
docs/analyze-data/explore/cypher-supported.mdx (1)
531-583: 💤 Low valueOptional: Consider varying sentence structure for improved readability.
The static analysis tool notes that multiple function descriptions begin with "Returns..." While this repetitive structure is acceptable and even helpful in technical reference documentation for quick scanning, you could optionally vary the phrasing if preferred.
Alternative phrasing examples
nodes: "Extracts all nodes from a matched path in order."relationships: "Extracts the relationship list from a path in order."startNode: "Gets the source node of a relationship."endNode: "Gets the target node of a relationship."However, the current consistent phrasing is perfectly acceptable for reference documentation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/analyze-data/explore/cypher-supported.mdx` around lines 531 - 583, The descriptions for functions nodes, relationships, startNode, endNode, head, and tail all start with the same "Returns..." phrasing; optionally vary these to improve readability by rewording each sentence (e.g., "Extracts all nodes from a matched path" for nodes, "Gets the source node of a relationship" for startNode, etc.) while preserving the examples and technical meaning; update the text around the function names nodes, relationships, startNode, endNode, head, and tail to use varied verb choices and maintain consistent tense and brevity across entries.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/analyze-data/explore/cypher-supported.mdx`:
- Around line 127-131: The ORDER BY example currently uses UNWIND before UNWIND
is documented; replace the UNWIND-based snippet (WITH [2, 3, 1, 5, 4] AS list /
UNWIND list AS num / RETURN num / ORDER BY num DESC) with a simpler example that
doesn't rely on UNWIND, e.g. a cypher query using MATCH such as MATCH (u:User) /
RETURN u.name / ORDER BY u.name DESC / LIMIT 10, or alternatively move the
UNWIND section earlier so UNWIND is introduced before the "Result Ordering and
Pagination" section; update the example in the file to use the
MATCH/RETURN/ORDER BY/LIMIT form if you choose the first option.
In `@docs/resources/release-notes/summary.mdx`:
- Line 36: Remove the duplicated word in the release notes row that currently
reads "the the reserved `tag_` prefix" and change it to "the reserved `tag_`
prefix" so the sentence reads correctly in the OpenGraph table entry (the string
containing "the the reserved `tag_` prefix" should be updated).
In `@docs/snippets/cypher-mutations.mdx`:
- Around line 1-3: Update the configuration link anchor in
docs/snippets/cypher-mutations.mdx by changing the fragment identifier from
`#enable_cypher_mutations` to `#enable-cypher-mutations` in the BloodHound
configuration file link so it matches the hyphenated anchor style used elsewhere
(e.g., `/manage-bloodhound/bh-config#enable-cypher-mutations`) and replace the
existing `enable_cypher_mutations` anchor occurrence accordingly.
---
Nitpick comments:
In `@docs/analyze-data/explore/cypher-supported.mdx`:
- Around line 531-583: The descriptions for functions nodes, relationships,
startNode, endNode, head, and tail all start with the same "Returns..."
phrasing; optionally vary these to improve readability by rewording each
sentence (e.g., "Extracts all nodes from a matched path" for nodes, "Gets the
source node of a relationship" for startNode, etc.) while preserving the
examples and technical meaning; update the text around the function names nodes,
relationships, startNode, endNode, head, and tail to use varied verb choices and
maintain consistent tense and brevity across entries.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f00c82cb-ec1f-4777-92c7-42558007befa
⛔ Files ignored due to path filters (3)
docs/images/release_notes/9_2_0/eligible-roles.pngis excluded by!**/*.pngdocs/images/release_notes/9_2_0/exposure-tooltip.pngis excluded by!**/*.pngdocs/images/release_notes/9_2_0/search-selection.gifis excluded by!**/*.gif
📒 Files selected for processing (10)
docs/analyze-data/explore/cypher-supported.mdxdocs/assets/opengraph/opengraph-node.jsondocs/docs.jsondocs/opengraph/developer/edges.mdxdocs/opengraph/developer/graph-definition.mdxdocs/opengraph/developer/nodes.mdxdocs/resources/release-notes/2026-05-26.mdxdocs/resources/release-notes/summary.mdxdocs/snippets/cypher-mutations.mdxdocs/snippets/opengraph/reserved-prefix.mdx
StephenHinck
left a comment
StephenHinck
left a comment
There was a problem hiding this comment.
Left several comments for review/update
Co-authored-by: Stephen Hinck <shinck@specterops.io>
StephenHinck
left a comment
StephenHinck
left a comment
There was a problem hiding this comment.
Looks great, SHIP IT
2 participants
Purpose
This pull request (PR) adds release notes for the May 6, 2026 release to the release integration branch, which includes:
No release for:
Staging
Summary by CodeRabbit
nodes,relationships,startNode,endNode,head,tail) and clauses (WITH,ORDER BY,SKIP,LIMIT,UNWIND).tag_prefix (case-insensitive).