Dynamic Matrix Update

The Dynamic Matrix Updater (matrix_update.py) automatically updates your matrix configuration with the latest or stable language versions from official sources.

Overview

This component eliminates the need for manual version updates in your testing matrices. It fetches language version information from official APIs and updates your matrix JSON file based on specified strategies, ensuring your CI/CD workflows always test against relevant language versions.

graph TD
    Start[json2vars-setter Action] -->|Input Parameters| Condition{update-matrix?}

    %% False path - direct JSON parsing
    Condition -->|false| G[github_output.py]

    %% True path - update then parse
    Condition -->|true| Step1[Read JSON File<br>#40;If not specified, read in matrix.json#41;]
    Step1 --> Step2[Fetch from GitHub API]
    Step2 --> Step3[Filter by Strategy]
    Step3 --> Step4[Update JSON File]
    Step4 --> G

    %% Common final step
    G -->|Set| H[GitHub Actions Outputs]

    %% 中央配置の設定
    linkStyle default stroke-width:2px

    classDef condition fill:#42a5f5,stroke:#1976d2,stroke-width:1px,color:#fff
    classDef process fill:#43a047,stroke:#2e7d32,stroke-width:2px,color:#fff
    classDef api fill:#e91e63,stroke:#c2185b,stroke-width:1px,color:#fff
    classDef json fill:#ffca28,stroke:#fb8c00,stroke-width:1px,color:#333333
    classDef output fill:#42a5f5,stroke:#1976d2,stroke-width:1px,color:#fff
    classDef start fill:#9c27b0,stroke:#6a1b9a,stroke-width:2px,color:#fff

    class Start start
    class Condition condition
    class Step2 api
    class Step1,Step3,G process
    class Step4 json
    class H output

Features

Update Strategies

The updater provides flexible version selection through three distinct strategies:

1. stable: Include only stable versions of the language

   • Ideal for production environments and critical workflows
   • Focuses on reliability and backward compatibility

2. latest: Include only the latest versions (including pre-releases)

   • Perfect for cutting-edge testing and forward compatibility checks
   • Ensures your code works with upcoming language releases

3. both: Include both stable and latest versions

   • Comprehensive coverage for both stability and future-proofing
   • Best for libraries and frameworks that need wide compatibility

Configurable Per Language

One of the key advantages is the ability to specify different update strategies for each supported language, giving you fine-grained control over your testing matrix:

1
2
3
4
5
6
7
8
9

- name: Set variables from dynamically updated JSON
  id: json2vars
  uses: 7rikazhexde/json2vars-setter@v1.13.0
  with:
    json-file: .github/json2vars-setter/sample/matrix.json
    update-matrix: 'true'
    python-strategy: 'stable'
    nodejs-strategy: 'latest'
    ruby-strategy: 'both'

Dry Run Mode

Test your update strategies without modifying your JSON file using the dry-run option:

1
2
3
4
5
6
7
8

- name: Test dynamic update without changing files
  id: json2vars
  uses: 7rikazhexde/json2vars-setter@v1.13.0
  with:
    json-file: .github/json2vars-setter/sample/matrix.json
    update-matrix: 'true'
    update-strategy: 'latest'
    dry-run: 'true'

This helps you verify your configuration and see what changes would be made before committing to them.

Backup Creation

The updater automatically creates a backup of your original matrix file before making changes, providing an easy fallback if needed.

Usage Examples

Basic Example

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

name: Use Dynamic Matrix Update

jobs:
  build_and_test:
    runs-on: ubuntu-latest
    outputs:
      os: ${{ steps.json2vars.outputs.os }}
      versions_python: ${{ steps.json2vars.outputs.versions_python }}
    steps:
      - name: Checkout repository
        uses: actions/checkout@v7.0.1

      - name: Set variables with dynamic update
        id: json2vars
        uses: 7rikazhexde/json2vars-setter@v1.13.0
        with:
          json-file: .github/json2vars-setter/sample/matrix.json
          update-matrix: 'true'
          update-strategy: 'latest'

      # Use the outputs directly
      - name: Display matrix info
        run: |
          echo "OS: ${{ steps.json2vars.outputs.os }}"
          echo "Python versions: ${{ steps.json2vars.outputs.versions_python }}"

Language-Specific Strategies

You can mix and match update strategies for different languages:

1
2
3
4
5
6
7
8
9

- name: Set variables with mixed update strategies
  id: json2vars
  uses: 7rikazhexde/json2vars-setter@v1.13.0
  with:
    json-file: .github/json2vars-setter/sample/matrix.json
    update-matrix: 'true'
    python-strategy: 'stable'
    nodejs-strategy: 'latest'
    go-strategy: 'both'

Periodic Updates with Scheduled Workflows

Create a scheduled workflow to keep your matrix up-to-date automatically:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

name: Update Matrix Weekly

on:
  schedule:
    - cron: '0 0 * * 0'  # Run every Sunday at midnight

jobs:
  update_matrix:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v7.0.1

      - name: Update matrix.json
        uses: 7rikazhexde/json2vars-setter@v1.13.0
        with:
          json-file: .github/json2vars-setter/sample/matrix.json
          update-matrix: 'true'
          update-strategy: 'stable'

      - name: Commit changes
        run: |
          git config --local user.email "actions@github.com"
          git config --local user.name "GitHub Actions"
          git add .github/json2vars-setter/matrix.json
          git commit -m "Update testing matrix with latest stable versions" || echo "No changes to commit"
          git push

Input Parameters

The Dynamic Matrix Updater accepts the following inputs:

How It Works

When you set update-matrix: 'true', the action performs these steps internally:

1. Load Existing Configuration: The specified JSON file is loaded to retain its structure
2. Fetch Version Information: For each language with a specified strategy, it contacts the official API
3. Apply Update Strategy: Versions are filtered based on the specified strategy for each language
4. Create a Backup: Before making changes, a backup of the original file is created (unless in dry-run mode)
5. Update the Matrix: The JSON file is updated with the new version information
6. Parse JSON: The updated JSON file is processed by github_output.py
7. Set Outputs: The values from the JSON file are set as GitHub Actions outputs

sequenceDiagram
    participant Workflow as GitHub Workflow
    participant Action as json2vars-setter
    participant Updater as matrix_update.py
    participant Parser as github_output.py
    participant API as Language APIs
    participant File as matrix.json

    Workflow->>Action: Run with update-matrix: 'true'
    Action->>Updater: Execute with strategies
    Updater->>File: Read existing config

    loop For each language
        Updater->>API: Fetch version info
        API->>Updater: Return versions
        Updater->>Updater: Filter by strategy
    end

    Updater->>File: Backup original (if not dry-run)
    Updater->>File: Update with new versions
    Updater->>Action: Return control
    Action->>Parser: Execute with updated JSON
    Parser->>File: Read updated JSON
    Parser->>Workflow: Set GitHub outputs

Supported Languages

The Dynamic Matrix Updater currently supports:

• Python: Fetches from Python releases via GitHub API
• Node.js: Fetches from Node.js releases via GitHub API
• Ruby: Fetches from Ruby releases via GitHub API
• Go: Fetches from Go releases via GitHub API
• Rust: Fetches from Rust releases via GitHub API
• PHP: Fetches from PHP releases via GitHub API
• .NET (C#): Fetches from .NET SDK releases via GitHub API
• Java: Fetches from the Adoptium API (latest feature release / latest LTS)
• Deno: Fetches from Deno releases via GitHub API
• Bun: Fetches from Bun releases via GitHub API
• Zig: Fetches from Zig releases via GitHub API
• Elixir: Fetches from Elixir releases via GitHub API
• Dart: Fetches from the Dart SDK release archive
• Swift: Fetches from the swift.org install API
• Julia: Fetches from Julia releases via GitHub API
• Crystal: Fetches from Crystal releases via GitHub API
• Haskell: Fetches from GHC releases via GitHub API
• OCaml: Fetches from OCaml releases via GitHub API
• Kotlin: Fetches from Kotlin releases via GitHub API (JetBrains/kotlin)
• Clang: Fetches from LLVM releases via GitHub API (llvm/llvm-project)
• GCC: Fetches from GCC releases via GitHub API (gcc-mirror/gcc)
• Flutter: Fetches from the official Flutter release manifest (stable channel)

Best Practices

• Use dry-run: 'true' to test your update strategy before implementing it
• Create a scheduled workflow to update your matrix on a regular basis (weekly or monthly)
• For critical workflows, use the stable strategy to avoid potential issues with latest releases
• For bleeding-edge testing, use the latest strategy
• For libraries and frameworks, use the both strategy to ensure wide compatibility
• Set up automated commits after updates to keep your repository in sync
• Consider combining with version caching for larger projects to optimize API usage (

Common Issues and Solutions

Next Steps

• Learn how to version caching your matrix configurations
• See basic examples of complete workflow configurations
• Review the command options reference for all available options