chore: Upgrade cache action to v4, bump CACHE_SEED

[tedil]

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions cache version from v3 to v4 across multiple workflow files
  • Modified cache seed value in build artifacts workflow

[coderabbitai]

Walkthrough

The pull request introduces a comprehensive update to GitHub Actions workflows across multiple action configuration files. The primary change involves upgrading the actions/cache action from version 3 to version 4 in several GitHub Actions files, including acmg-class-by-freq, convert-clinvar, download-clinvar, extract-vars, gene-variant-report, and phenotype-links. Additionally, the -build-artifacts.yml workflow file has been modified to change the CACHE_SEED environment variable from "0" to "1".

Changes

File	Change Summary
.github/actions/*/action.yml	Upgraded actions/cache from v3 to v4 in multiple steps across different action files
.github/workflows/-build-artifacts.yml	Updated CACHE_SEED environment variable from "0" to "1"

Poem

🐰 Cache update, version four,
Workflows dancing through the core,
Rabbit hops with glee so bright,
Caching magic takes its flight!
GitHub Actions, smooth and clean,
A technological dream! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c69913 and 0cf118a.

📒 Files selected for processing (7)

• .github/actions/acmg-class-by-freq/action.yml (2 hunks)
• .github/actions/convert-clinvar/action.yml (2 hunks)
• .github/actions/download-clinvar/action.yml (1 hunks)
• .github/actions/extract-vars/action.yml (2 hunks)
• .github/actions/gene-variant-report/action.yml (2 hunks)
• .github/actions/phenotype-links/action.yml (2 hunks)
• .github/workflows/-build-artifacts.yml (1 hunks)

✅ Files skipped from review due to trivial changes (3)

• .github/actions/phenotype-links/action.yml
• .github/actions/download-clinvar/action.yml
• .github/actions/convert-clinvar/action.yml

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Build-Artifacts / Convert-Clinvar

🔇 Additional comments (4)

.github/actions/extract-vars/action.yml (1)

25-25: LGTM! Cache action upgrades look good.

The upgrade to actions/cache@v4 is consistently applied across all caching steps, maintaining proper cache key generation with CACHE_SEED.

Also applies to: 50-50, 58-58

.github/actions/acmg-class-by-freq/action.yml (1)

25-25: LGTM! Cache action upgrades are consistent.

The upgrade pattern matches extract-vars/action.yml, maintaining consistency across actions.

Also applies to: 50-50, 58-58

.github/actions/gene-variant-report/action.yml (1)

25-25: LGTM! Cache action upgrades maintain consistency.

The upgrade pattern continues to be consistent with other action files.

Also applies to: 50-50, 58-58

.github/workflows/-build-artifacts.yml (1)

31-31: LGTM! Cache invalidation strategy is appropriate.

Bumping CACHE_SEED from "0" to "1" will properly invalidate all existing caches, forcing regeneration with the new cache action version.

Let's verify that all cache actions have been upgraded consistently:

✅ Verification successful

Cache action upgrade verification successful

All instances of actions/cache have been consistently upgraded to v4 across the codebase.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that all cache actions use v4
# Test: Search for any remaining v3 cache actions. Expect: No results.
rg "actions/cache@v3" .github/

# Test: Confirm all cache actions are using v4. Expect: Multiple matches.
rg "actions/cache@v4" .github/

Length of output: 1299

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.