Update arabica_versions.js #1796
Conversation
WalkthroughThe pull request modifies the Changes
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (3).vitepress/constants/arabica_versions.js (3)Line range hint The changes maintain the expected structure and immutability pattern. The version bump appears correct, but final approval should wait for the verification of SHA authenticity and documentation consistency checks.
The version bump from v0.20.1-arabica to v0.20.2-arabica looks correct, but let's verify the SHA corresponds to the correct tag in the repository. ✅ Verification successfulSHA verification successful The SHA 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify the SHA matches the tag in celestia-node repository
# Expected: The SHA should match the tagged commit
# Check if the tag exists and get its SHA
gh api repos/celestiaorg/celestia-node/git/refs/tags/v0.20.2-arabica | jq -r '.object.sha'
# Verify the commit details
gh api repos/celestiaorg/celestia-node/git/commits/2dc9cce7b5dffc14fd4fe156d2aa9869318e0f68 | jq -r '.message'
Length of output: 812 Line range hint Since this is a version update in the documentation, we should verify that all references to the node version are consistent throughout the docs. ✅ Verification successfulVersion update appears to be properly isolated The version update to 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check for any outdated version references in documentation
# Expected: No instances of the old version should remain
# Search for old version references
rg "v0.20.1-arabica" --type md --type js
# Search for new version to ensure it's properly referenced where needed
rg "v0.20.2-arabica" --type md --type js
Length of output: 81 Script: #!/bin/bash
# Let's try a broader search to find any version references in the docs
# First, let's find all documentation files
fd -e md -e mdx
# Then search for any version patterns that might be related to node
rg -i "node.*version|version.*node" --type md --type mdx -A 2 -B 2
# Also search for any arabica version patterns
rg "v[0-9]+\.[0-9]+\.[0-9]+-arabica" --type md --type mdx
Length of output: 2945 Script: #!/bin/bash
# Let's search specifically in markdown files and the constants directory
# Search for any version patterns in markdown files
rg "v[0-9]+\.[0-9]+\.[0-9]+-arabica" --type md
# Search for node version references in markdown files
rg -i "node.*v0\.20\." --type md
# Check the constants directory for other version files
fd . .vitepress/constants/ -t f
# Look for version references in any JavaScript files in the constants directory
rg "v[0-9]+\.[0-9]+\.[0-9]+" .vitepress/constants/
Length of output: 1380 Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Overview
Summary by CodeRabbit
New Features
Bug Fixes