Skip to content

[GH Action] Update release tags and commit SHAs for arabica & mainnet#2125

Merged
jcstein merged 3 commits intomainfrom
create-pull-request/patch
Jun 30, 2025
Merged

[GH Action] Update release tags and commit SHAs for arabica & mainnet#2125
jcstein merged 3 commits intomainfrom
create-pull-request/patch

Conversation

@celestia-bot
Copy link
Copy Markdown
Contributor

Automated changes by create-pull-request GitHub action

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @celestia-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the release tags and commit SHAs for the arabica versions in the .vitepress/constants/arabica_versions.js file. The updates involve changing the app and node versions from arabica to mocha, along with their corresponding SHAs.

Highlights

  • Dependency Update: Updated the app-latest-tag from v4.0.6-arabica to v4.0.6-mocha.
  • Dependency Update: Updated the app-latest-sha from e8532b64d1f4fd31ea4764d8df21ee52c566abd3 to b95a0c9fb34beba47f802cdba2de690dc6f50711.
  • Dependency Update: Updated the node-latest-tag from v0.23.0-arabica to v0.23.2-mocha.
  • Dependency Update: Updated the node-latest-sha from b814f44afb5bde01b3714c4f21fe34203d90405d to 13f44136b2d3c8d46acf9a94de4dec3837253799.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jun 30, 2025

PR Preview Action v1.6.1
Preview removed because the pull request was closed.
2025-06-30 18:21 UTC

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request, an automated change, updates version tags and commit SHAs. However, the changes introduce 'mocha' specific versions into a file named arabica_versions.js, which contradicts the file's name and the pull request title. This inconsistency is a significant maintainability concern and could lead to incorrect version usage.

Comment on lines +2 to +5
"app-latest-tag": "v4.0.6-mocha",
"app-latest-sha": "b95a0c9fb34beba47f802cdba2de690dc6f50711",
"node-latest-tag": "v0.23.2-mocha",
"node-latest-sha": "13f44136b2d3c8d46acf9a94de4dec3837253799",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

The file .vitepress/constants/arabica_versions.js is being updated with version tags and SHAs that are explicitly for mocha. This contradicts the file's name, which suggests it should contain arabica versions, and also the pull request title, which states the update is for arabica. This inconsistency can lead to significant confusion and potential errors if other parts of the system rely on this file to provide arabica specific constants.

Suggested change
"app-latest-tag": "v4.0.6-mocha",
"app-latest-sha": "b95a0c9fb34beba47f802cdba2de690dc6f50711",
"node-latest-tag": "v0.23.2-mocha",
"node-latest-sha": "13f44136b2d3c8d46acf9a94de4dec3837253799",
"app-latest-tag": "v4.0.6-arabica",
"app-latest-sha": "e8532b64d1f4fd31ea4764d8df21ee52c566abd3",
"node-latest-tag": "v0.23.0-arabica",
"node-latest-sha": "b814f44afb5bde01b3714c4f21fe34203d90405d",

Comment thread .vitepress/constants/arabica_versions.js Outdated
Comment thread .vitepress/constants/arabica_versions.js Outdated
Comment thread .vitepress/constants/arabica_versions.js Outdated
Comment thread .vitepress/constants/arabica_versions.js Outdated
@jcstein jcstein changed the title [GH Action] Update release tags and commit SHAs for arabica [GH Action] Update release tags and commit SHAs for arabica & mainnet Jun 30, 2025
@jcstein jcstein merged commit 725d630 into main Jun 30, 2025
9 checks passed
@jcstein jcstein deleted the create-pull-request/patch branch June 30, 2025 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants