Fix install

[johnnyhuy]

PR Type

Enhancement, Configuration changes

---

Description

• Updated GitHub Actions workflows (build.yml, publish.yml, release.yml) to improve caching by including yarn.lock hash and added make install steps.
• Refactored Makefile to add conditional yarn install for CI environments and removed install dependency from lint, test, and dev targets.
• Added new targets in Makefile for GitHub Actions workflow triggers.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	build.yml Optimize build workflow with improved caching and installation. .github/workflows/build.yml Updated cache keys to include yarn.lock hash. Added make install step before linting and testing. +7/-2      publish.yml Optimize publish workflow with improved caching and installation. .github/workflows/publish.yml Updated cache keys to include yarn.lock hash. Added make install step before publishing. +7/-2      release.yml Optimize release workflow with improved caching and installation. .github/workflows/release.yml Updated cache keys to include yarn.lock hash. Added make install step before publishing and releasing. +7/-2
Enhancement	Makefile Refactor Makefile for CI environment and new targets.        Makefile Added conditional yarn install for CI environments. Removed install dependency from lint, test, and dev targets. Added new targets for GitHub Actions workflow triggers. +10/-4

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[echohello-codium-ai-pr-agent]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are mostly configuration updates and straightforward Makefile adjustments. The modifications are clear and localized to specific workflow files and the Makefile, which simplifies the review process.
🧪 Relevant tests	No
⚡ Possible issues	Possible Bug: The conditional yarn install in the Makefile might not work as expected if the CI environment variable is not set properly in all CI environments. This could lead to inconsistent dependency installations.
🔒 Security concerns	No

[echohello-codium-ai-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Ensure robustness by explicitly comparing the CI environment variable against the string "true" The conditional check for CI environment variable should explicitly compare against the expected value to avoid potential issues with different shell environments or configurations where the variable might be set but not strictly to 'true'. Makefile [22-25] -ifeq ($(CI),true) +ifeq ($(CI), "true") yarn install --immutable else yarn install Suggestion importance[1-10]: 9 Why: Explicitly comparing the CI environment variable against the string "true" improves robustness and avoids potential issues with different shell environments, which is crucial for maintainability.	9
Enhancement	Improve cache key uniqueness by including environment-specific identifiers To ensure cache keys are unique and relevant, include a more specific identifier for the runner environment, such as the runner's OS version or specific environment tags, instead of just the OS name. This will help in avoiding cache collisions across different environments that share the same OS but may have different configurations. .github/workflows/build.yml [28] -key: ${{ runner.os }}-${{ hashFiles('.tool-versions') }}-${{ hashFiles('yarn.lock') }} +key: ${{ runner.os }}-${{ env.RUNNER_ENV_TAG }}-${{ hashFiles('.tool-versions') }}-${{ hashFiles('yarn.lock') }} Suggestion importance[1-10]: 8 Why: Including environment-specific identifiers in the cache key can help avoid cache collisions and ensure more accurate caching, which is a significant improvement for build reliability.	8
Best practice	Standardize cache keys and restore-keys across workflows for consistent caching behavior To avoid redundancy and maintain consistency, align the cache key and restore-keys format across all workflow files. This ensures that all workflows behave similarly in terms of caching, which simplifies maintenance and debugging. .github/workflows/release.yml [34-38] -key: ${{ runner.os }}-${{ hashFiles('.tool-versions') }}-${{ hashFiles('yarn.lock') }} +key: ${{ runner.os }}-${{ env.RUNNER_ENV_TAG }}-${{ hashFiles('.tool-versions') }}-${{ hashFiles('yarn.lock') }} restore-keys: | - ${{ runner.os }}- - ${{ runner.os }}-${{ hashFiles('.tool-versions') }}- ${{ runner.os }}-${{ hashFiles('.tool-versions') }}-${{ hashFiles('yarn.lock') }} Suggestion importance[1-10]: 8 Why: Aligning the cache key and restore-keys format across all workflow files ensures consistency and simplifies maintenance and debugging, which is a best practice for workflow management.	8
Performance	Streamline the restore-keys to improve cache restoration efficiency Consider simplifying the restore-keys to avoid unnecessary cache restoration steps which can lead to slower build times if multiple keys match. Use a more streamlined approach to match the most relevant cache. .github/workflows/publish.yml [40-43] restore-keys: | - ${{ runner.os }}- - ${{ runner.os }}-${{ hashFiles('.tool-versions') }}- ${{ runner.os }}-${{ hashFiles('.tool-versions') }}-${{ hashFiles('yarn.lock') }} Suggestion importance[1-10]: 7 Why: Simplifying the restore-keys can improve build performance by reducing unnecessary cache restoration steps, which is beneficial but not critical.	7