Conversation
## Motivation #2034 (comment) Context in #2034 (comment)
WalkthroughThe Changes
Possibly related PRs
Suggested reviewers
Poem
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. ✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| "core-latest-tag": "v1.53.0-tm-v0.38.17", | ||
| "core-latest-sha": "4acfd99c3893123775c533465f164f771d3a6f15", |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Confirm updated core version tag and SHA values
Please verify that the tag v1.53.0-tm-v0.38.17 exists in the celestia-core repository and that it points to commit 4acfd99c3893123775c533465f164f771d3a6f15.
🏁 Script executed:
#!/usr/bin/env bash
REPO="https://github.com/celestia-core/celestia-core.git"
TAG="v1.53.0-tm-v0.38.17"
EXPECTED="4acfd99c3893123775c533465f164f771d3a6f15"
# Fetch the commit SHA for the tag without cloning
RES=$(git ls-remote "$REPO" "refs/tags/$TAG" | awk '{print $1}')
echo "Tag $TAG -> $RES"
if [ "$RES" != "$EXPECTED" ]; then
echo "ERROR: SHA mismatch for $TAG (expected $EXPECTED)"
exit 1
else
echo "✅ SHA matches expected value"
fiLength of output: 706
Let's verify against both possible GitHub org paths to locate the tag and SHA:
🏁 Script executed:
#!/usr/bin/env bash
TAG="v1.53.0-tm-v0.38.17"
EXPECTED="4acfd99c3893123775c533465f164f771d3a6f15"
for ORG in "celestia-core" "celestia"; do
REPO="https://github.com/$ORG/celestia-core.git"
echo "Checking $REPO..."
SHA=$(git ls-remote "$REPO" "refs/tags/$TAG" 2>/dev/null | awk '{print $1}')
if [ -z "$SHA" ]; then
echo " – Tag not found in $REPO"
else
echo " – Tag $TAG → $SHA"
if [ "$SHA" = "$EXPECTED" ]; then
echo " ✅ SHA matches expected in $REPO"
else
echo " ❌ SHA mismatch in $REPO (expected $EXPECTED)"
fi
fi
doneLength of output: 1101
Tag v1.53.0-tm-v0.38.17 not found – please correct core version and SHA
We attempted to locate v1.53.0-tm-v0.38.17 in both celestia-core/celestia-core and celestia/celestia-core, but the tag does not exist in either repo. Please verify that the correct repository, tag name, and commit SHA are being used and update the values accordingly.
• File: .vitepress/constants/arabica_versions.js
Lines: 4–5
"core-latest-tag": "v1.53.0-tm-v0.38.17",
"core-latest-sha": "4acfd99c3893123775c533465f164f771d3a6f15",
|
|
Thank you, LGTM. FWIW we don't use these core variables so note to self to remove them eventually |
2 participants
Addresses #2034 (comment)
Context in #2034 (comment)
Summary by CodeRabbit