Update neo4j docs examples to latest supported version (2025.12.1)#924
Conversation
Bump the neo4j example/guide manifests to the latest supported version per installer active_versions.json. Deploy examples use the latest; version-upgrade guides keep an older source and upgrade to the latest. Illustrative command outputs and other products' versions are left unchanged. Signed-off-by: Tamal Saha <tamal@appscode.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✅ Files skipped from review due to trivial changes (4)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAll Neo4j ChangesNeo4j version bump to 2025.12.1
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
![kodiak-appscode[bot]](https://avatars.githubusercontent.com/in/92481?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (2)
docs/guides/neo4j/restart/restart.md (1)
40-40: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winConsider updating illustrative output to match deployed version.
Line 40 deploys
2025.12.1, but the examplekubectl getoutput at Line 64 still shows2025.10.1. While the PR objectives state illustrative outputs are left unchanged, this creates a user-facing inconsistency in the same guide where the deployment manifest and expected output show different versions.If the intent is to show realistic output, consider updating the VERSION column in the example output to match the deployed version.
Also applies to: 63-65
🤖 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/guides/neo4j/restart/restart.md` at line 40, Update the illustrative kubectl get output in the neo4j restart guide so it matches the deployed version shown in the manifest. The inconsistency is between the version value used in the deployment example and the VERSION column in the expected output; adjust the example output near the kubectl snippet to reflect 2025.12.1, keeping the guide’s version references aligned. Use the existing deployment/version examples in the restart guide as the reference point when editing the output block.docs/guides/neo4j/rotate-auth/rotateauth.md (1)
60-60: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winConsider updating illustrative output to match deployed version.
Line 60 deploys
2025.12.1, but the examplekubectl getoutput at Line 84 still shows2025.10.1. This creates a user-facing inconsistency where the deployment manifest and expected output show different versions.Consider updating the VERSION column in the example output to match the deployed version for consistency.
Also applies to: 83-85
🤖 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/guides/neo4j/rotate-auth/rotateauth.md` at line 60, The example kubectl output in the rotate-auth guide is inconsistent with the deployed Neo4j version, so update the illustrative VERSION value to match the manifest version used by the deployment. Adjust the expected output near the kubectl get example so it reflects 2025.12.1 consistently, and keep the surrounding example text in sync with the rotate-auth walkthrough.
🤖 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.
Nitpick comments:
In `@docs/guides/neo4j/restart/restart.md`:
- Line 40: Update the illustrative kubectl get output in the neo4j restart guide
so it matches the deployed version shown in the manifest. The inconsistency is
between the version value used in the deployment example and the VERSION column
in the expected output; adjust the example output near the kubectl snippet to
reflect 2025.12.1, keeping the guide’s version references aligned. Use the
existing deployment/version examples in the restart guide as the reference point
when editing the output block.
In `@docs/guides/neo4j/rotate-auth/rotateauth.md`:
- Line 60: The example kubectl output in the rotate-auth guide is inconsistent
with the deployed Neo4j version, so update the illustrative VERSION value to
match the manifest version used by the deployment. Adjust the expected output
near the kubectl get example so it reflects 2025.12.1 consistently, and keep the
surrounding example text in sync with the rotate-auth walkthrough.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ad53bfc1-2a0c-4ea0-881e-8a5e7be51425
📒 Files selected for processing (9)
docs/examples/neo4j/quickstart/neo4j.yamldocs/guides/neo4j/backup/kubestash/customization/common/sample-neo4j.yamldocs/guides/neo4j/backup/kubestash/logical/examples/restored-neo4j.yamldocs/guides/neo4j/backup/kubestash/logical/examples/sample-neo4j.yamldocs/guides/neo4j/backup/kubestash/logical/index.mddocs/guides/neo4j/monitoring/using-prometheus-operator.mddocs/guides/neo4j/private-registry/using-private-registry.mddocs/guides/neo4j/restart/restart.mddocs/guides/neo4j/rotate-auth/rotateauth.md
Signed-off-by: Fazle Rabbi Sarker <fazlerabbi@appscode.com>
fr-sarker
dismissed stale reviews from kodiak-appscode[bot] and themself
via
7a9c3eb
|
Visit the preview URL for this PR (updated for commit 8b4ea5f): https://kubedb-v2-hugo--pr924-update-neo4j-docs-ve-qlmaut2d.web.app (expires Thu, 09 Jul 2026 05:42:31 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 0f29ae8ae0bd54a99bf2b223b6833be47acd5943 |
2 participants
Bumps the neo4j example and guide manifests to the latest supported version (
2025.12.1) per the installeractive_versions.json.kubectl get ...versiontables,describedumps) and other products'/backend versions are left unchanged.Summary by CodeRabbit