auto-docs: Update property docs for tag v26.1.7#1693
auto-docs: Update property docs for tag v26.1.7#1693vbotbuildovich wants to merge 1 commit intomainfrom
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThis PR documents the addition of the new Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsTimed out fetching pipeline failures after 30000ms Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@antora.yml`:
- Around line 20-21: The metadata currently sets full-version: 26.1.7 and
latest-redpanda-tag: 'v26.1.7' but latest-release-commit is pointing to the
wrong SHA; update the latest-release-commit value to the correct commit SHA
b85ee3cde96881e289beb114f1fbdfe103f4c6e9 so it matches the v26.1.7 tag (look for
the latest-release-commit key in the same file and replace its value).
🪄 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: 804bd291-e525-42c1-8a65-e6a449b10203
📒 Files selected for processing (5)
antora.ymldocs-data/property-overrides.jsondocs-data/redpanda-property-changes-v26.1.6-to-v26.1.7.jsonmodules/reference/attachments/redpanda-properties-v26.1.7.jsonmodules/reference/partials/properties/cluster-properties.adoc
| full-version: 26.1.7 | ||
| latest-redpanda-tag: 'v26.1.7' |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify that tag v26.1.7 exists in redpanda-data/redpanda repository
# and check if the commit hash needs updating.
# Check if tag v26.1.7 exists
echo "Checking if tag v26.1.7 exists..."
gh api repos/redpanda-data/redpanda/git/refs/tags/v26.1.7 --jq '{tag: .ref, commit: .object.sha}' 2>&1
# Get the current commit hash from the file for comparison
echo -e "\nCurrent commit hash in antora.yml: 35a825c9c1880ebeedf4c18bb8c6cceaa63566c1"Repository: redpanda-data/docs
Length of output: 253
Update latest-release-commit to match the v26.1.7 tag.
The tag v26.1.7 exists in the Redpanda repository, but points to commit b85ee3cde96881e289beb114f1fbdfe103f4c6e9. Line 23 has latest-release-commit: '35a825c9c1880ebeedf4c18bb8c6cceaa63566c1', which does not match. Update line 23 to point to the correct commit for this release.
🤖 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 `@antora.yml` around lines 20 - 21, The metadata currently sets full-version:
26.1.7 and latest-redpanda-tag: 'v26.1.7' but latest-release-commit is pointing
to the wrong SHA; update the latest-release-commit value to the correct commit
SHA b85ee3cde96881e289beb114f1fbdfe103f4c6e9 so it matches the v26.1.7 tag (look
for the latest-release-commit key in the same file and replace its value).
This PR auto-generates updated Redpanda property documentation for v26.1.7.