[GH Action] Update release tags and commit SHAs for mocha#2098
Conversation
WalkthroughThe Mocha version constants for the "node" environment in Changes
Possibly related PRs
Suggested reviewers
Poem
✨ 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}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.vitepress/constants/mocha_versions.js(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: build
- GitHub Check: Analyze (go)
| "node-latest-tag": "v0.23.1-mocha", | ||
| "node-latest-sha": "500bf455aba081561ecccf536d7b49f3a6f224b9", |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Verify updated node-latest-tag and node-latest-sha.
The Mocha release tag and SHA were bumped; please confirm that v0.23.1-mocha exists in the Mocha repo and that the SHA matches the actual commit. You can run:
🏁 Script executed:
#!/usr/bin/env bash
repo="https://github.com/mochajs/mocha.git"
tag="v0.23.1-mocha"
expected="500bf455aba081561ecccf536d7b49f3a6f224b9"
actual=$(git ls-remote "$repo" "refs/tags/${tag}^{}" | awk '{print $1}')
if [[ "$actual" != "$expected" ]]; then
echo "SHA mismatch: expected $expected, got $actual"
exit 1
fi
echo "Tag and SHA are valid."Length of output: 481
Let’s check if any v0.23.1-based tag (with or without the -mocha suffix) actually exists upstream:
🏁 Script executed:
#!/usr/bin/env bash
repo="https://github.com/mochajs/mocha.git"
git ls-remote --tags "$repo" | grep -E 'v0\.23\.1(-mocha)?'Length of output: 134
Invalid Mocha tag in .vitepress/constants/mocha_versions.js
It looks like the tag v0.23.1-mocha isn’t present upstream (no matching remote tag found), so the SHA can’t be verified. Please correct the node-latest-tag and node-latest-sha values to point at a valid Mocha release:
• File: .vitepress/constants/mocha_versions.js
• Lines: 4–5
Suggested next steps:
- Confirm the intended Mocha tag is published in https://github.com/mochajs/mocha.git (e.g. via
git ls-remote --tags). - Update
node-latest-tagto the existing tag name. - Update
node-latest-shato match the commit SHA of that tag.
🤖 Prompt for AI Agents
In .vitepress/constants/mocha_versions.js at lines 4 to 5, the current values
for node-latest-tag and node-latest-sha reference a non-existent Mocha tag
v0.23.1-mocha, causing a mismatch. To fix this, verify the correct existing
Mocha tag from the official Mocha GitHub repository, then update node-latest-tag
to that valid tag name and node-latest-sha to the corresponding commit SHA for
that tag.
2 participants
Automated changes by create-pull-request GitHub action
Summary by CodeRabbit