Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update mocha_versions.js #1765

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Update mocha_versions.js #1765

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .vitepress/constants/mocha_versions.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
const mochaVersions = Object.freeze({
"app-latest-tag": "v2.2.0-mocha",
"app-latest-sha": "d3f8b2997fcbc8e7f43785a9513b2d0c91675087",
"app-latest-tag": "v2.3.0-mocha",
"app-latest-sha": "17a756a20c5b96cc9c5e72fa09a7c0c33cb19f7b",
"core-latest-tag": "v1.40.1-tm-v0.34.29-rc0",
"core-latest-sha": "0d2b63836d0f4587e162bfded58f53fba238e69c",
"node-latest-tag": "v0.18.2-mocha",
"node-latest-sha": "4309c8349857638b033a2a278da0f8ab182fdb26",
"node-latest-tag": "v0.18.3-mocha",
"node-latest-sha": "395ba5fbfd1cd7f35ae3c13cf78902612b22c64f",
Comment on lines +6 to +7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Version tag and SHA are invalid and need to be updated

Based on the verification results:

  1. The SHA 395ba5fbfd1cd7f35ae3c13cf78902612b22c64f does not exist in the repository
  2. The tag v0.18.3-mocha does not exist in the repository
  3. No references to either the SHA or the version tag were found in the codebase

This indicates that the version tag and SHA in mocha_versions.js are incorrect and need to be updated with valid values that correspond to an actual release or commit in the repository.

🔗 Analysis chain

Verify node version tag and SHA correspondence.

The node version has been bumped from v0.18.2-mocha to v0.18.3-mocha (patch version update).

Let me try to verify this in a different way by checking the repository's tags and commits to get more context.

Let me try one final verification by checking if this version information might be referenced in other configuration files or documentation.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the SHA matches the tag for the node component
# Expected: The SHA should be associated with the v0.18.3-mocha tag

# Test: Check if the SHA exists in the repository
gh api repos/celestiaorg/docs/commits/395ba5fbfd1cd7f35ae3c13cf78902612b22c64f --silent || echo "SHA not found"

# Test: Check if the tag exists and points to the correct SHA
gh api repos/celestiaorg/docs/git/refs/tags/v0.18.3-mocha --jq '.object.sha' || echo "Tag not found"

Length of output: 478

Script:

#!/bin/bash
# Let's check all available tags in the repository that contain "mocha"
gh api repos/celestiaorg/docs/git/refs/tags --jq '.[].ref' | grep -i mocha || echo "No mocha tags found"

# Let's also check recent commits to see if we can find related changes
gh api repos/celestiaorg/docs/commits --jq '.[].commit.message' | head -n 5

Length of output: 492

Script:

#!/bin/bash
# Search for any references to these versions in the codebase
rg -l "v0.18.3-mocha|395ba5fbfd1cd7f35ae3c13cf78902612b22c64f"

# Check if there are any package.json or similar config files that might reference these versions
fd -e json -e yaml -e yml | xargs rg "0.18.3|395ba5fbfd"

# Look for any documentation files mentioning these versions
fd -e md | xargs rg "v0.18.3-mocha"

Length of output: 159

});
export default mochaVersions;
Loading