Update Meshery Catalog to Golang 1.25

[arhmm7]

This PR fixes #2472

1. Updated go directive in assets/artifact-hub-pkg/go.mod from 1.24.5 to 1.25
2. Updated Go version in GitHub Actions workflows:
   add-catalog.yml: 1.23 → 1.25
   error-code-updater.yml: 1.23 → 1.25

• Yes, I signed my commits.

[netlify]

✅ Deploy Preview for mesheryio-preview ready!

Name	Link
🔨 Latest commit	4df369c
🔍 Latest deploy log	https://app.netlify.com/projects/mesheryio-preview/deploys/695f71afb4af8b000843a825
😎 Deploy Preview	https://deploy-preview-2506--mesheryio-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gemini-code-assist]

Summary of Changes

Hello @arhmm7, I'm Gemini Code Assist¹! 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 upgrades the Go language version used across the Meshery Catalog. It specifically targets the go.mod file to reflect the new Go 1.25 requirement and updates relevant GitHub Actions workflows to utilize this newer version, ensuring the project benefits from the latest Go features and stability improvements.

Highlights

• Go Version Update: The go directive in assets/artifact-hub-pkg/go.mod has been updated from 1.24.5 to 1.25.
• GitHub Actions Update: The Go version used in add-catalog.yml and error-code-updater.yml GitHub Actions workflows has been updated from 1.23 to 1.25.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/add-catalog.yml
  • .github/workflows/error-code-updater.yml

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the project to use Go 1.25. The go.mod file is updated from version 1.24.5 to 1.25. As mentioned in the description, the GitHub Actions workflows are also updated from Go 1.23 to 1.25. This change not only brings the project up-to-date with a newer Go version but also improves consistency between the module's declared Go version and the CI environment. The change in the provided diff is correct and I have no further suggestions.

[kishore08-07]

@arhmm7
Thank you for your contribution!
Let's discuss this during the websites meet on 05/01/2026 at 6:30 PM IST | 7 AM CT
Add it as an agenda item to the meeting minutes, if you would :)