[GH Action] Update release tags and commit SHAs for arabica#1404
[GH Action] Update release tags and commit SHAs for arabica#1404
Conversation
WalkthroughThe update involves a version bump for a Node.js project, specifically changing the latest version tag and SHA hash in the Changes
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
jcstein
left a comment
There was a problem hiding this comment.
approved, but waiting to merge this until tomorrow once @celestiaorg/devops has updated arabica
|
There was a problem hiding this comment.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- .vitepress/constants/arabica_versions.js (1 hunks)
Additional comments: 1
.vitepress/constants/arabica_versions.js (1)
- 6-7: The updates to
node-latest-tagandnode-latest-shaare consistent with the PR objectives and follow the existing format used for other components in the file. Ensure that any downstream dependencies or configurations that rely on these values are also updated to reflect the new version of arabica.
Automated changes by create-pull-request GitHub action
Summary by CodeRabbit