fix: ci

[pthmas]

Overview

Fixing CI by using this branch of the evolve Ignite app: ignite/apps#248

[gemini-code-assist]

Summary of Changes

Hello @pthmas, 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 addresses continuous integration failures by standardizing the version of the ignite/apps/evolve application used in various Docker build environments. By pinning this dependency to a specific, known-good commit, it aims to enhance build reproducibility and stability, mitigating issues that could arise from unexpected changes on the main branch of the external repository.

Highlights

• Dependency Version Pinning: The IGNITE_EVOLVE_APP_VERSION has been updated across all relevant Dockerfiles to a specific commit hash (v0.0.0-20260203123550-097513a38337) instead of using the main branch.
• Build Argument Introduction: In Dockerfile and Dockerfile.cosmos-sdk, an ARG IGNITE_EVOLVE_APP_VERSION was introduced, allowing the version of the Ignite Evolve app to be specified at build time.
• Consistent Version Usage: The ignite app install commands and environment variables now consistently reference the IGNITE_EVOLVE_APP_VERSION build argument, ensuring the correct version is used throughout the build process.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• Dockerfile
  • Added ARG IGNITE_EVOLVE_APP_VERSION to allow specifying the evolve app version during the build process.
  • Updated ENV IGNITE_EVOLVE_APP_VERSION to dynamically use the value provided by the new build argument.
• Dockerfile.cosmos-sdk
  • Introduced ARG IGNITE_EVOLVE_APP_VERSION for build-time configuration of the evolve app version.
  • Added ENV IGNITE_EVOLVE_APP_VERSION to ensure the build argument's value is propagated as an environment variable.
  • Modified the ignite app install command to utilize the configurable IGNITE_EVOLVE_APP_VERSION.
• tests/integration/docker/Dockerfile.gm
  • Updated the default value of the IGNITE_EVOLVE_APP_VERSION argument to a specific, stable version.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

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 addresses a CI issue by pinning the ignite/apps/evolve dependency to a specific commit instead of the main branch. This is a good practice for ensuring reproducible builds. The changes are consistently applied across Dockerfile, Dockerfile.cosmos-sdk, and tests/integration/docker/Dockerfile.gm using a build argument. I've made a couple of suggestions to remove redundant ENV declarations in two of the Dockerfiles for better consistency and to adhere to Docker best practices. Otherwise, the changes look good.

[gemini-code-assist]

The IGNITE_EVOLVE_APP_VERSION is defined as a build argument (ARG) and is only used during the build process within this stage. Setting it as an environment variable (ENV) is redundant because ARG values are directly accessible in RUN instructions. For consistency and to follow Docker best practices, this ENV declaration can be removed. The tests/integration/docker/Dockerfile.gm file already follows this pattern.

[gemini-code-assist]

The IGNITE_EVOLVE_APP_VERSION is defined as a build argument (ARG) and is only used during the build process within this stage. Setting it as an environment variable (ENV) is redundant because ARG values are directly accessible in RUN instructions. For consistency and to follow Docker best practices, this ENV declaration can be removed.