Skip to content

fix: update windows release to docker buildx v4#32

Merged
varonix0 merged 1 commit intomainfrom
daniel/buildx-v3
Oct 10, 2025
Merged

fix: update windows release to docker buildx v4#32
varonix0 merged 1 commit intomainfrom
daniel/buildx-v3

Conversation

@varonix0
Copy link
Member

Updated buildx to v3

@varonix0 varonix0 self-assigned this Oct 10, 2025
@varonix0 varonix0 merged commit e940b83 into main Oct 10, 2025
3 checks passed
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greptile Overview

Summary

Updated the Windows release job to use docker/setup-buildx-action@v3 instead of v2 for building Windows Docker images.

  • Upgraded buildx version in goreleaser-windows job from v2 to v3
  • Note: PR title says "v4" but actual change is to v3
  • Main goreleaser job still uses buildx v2 at line 98, creating version inconsistency across the workflow

Confidence Score: 3/5

  • This PR is moderately safe to merge but has an inconsistency that should be addressed
  • The buildx upgrade to v3 for Windows is a valid improvement for compatibility, but the workflow now has mixed versions (v2 in goreleaser job, v3 in goreleaser-windows job). This inconsistency should be resolved by updating both jobs to v3 for uniformity.
  • .github/workflows/release_build_infisical_cli.yml - line 98 should be updated to match the Windows job's buildx version

Important Files Changed

File Analysis

Filename Score Overview
.github/workflows/release_build_infisical_cli.yml 3/5 Updated Windows job to use buildx v3, but inconsistency remains with main goreleaser job still on v2

Sequence Diagram

sequenceDiagram
    participant Tag as Git Tag Push
    participant WinJob as goreleaser-windows Job
    participant MainJob as goreleaser Job
    participant NPMJob as npm-release Job
    participant DockerHub as Docker Hub
    participant GitHub as GitHub Releases
    participant NPM as NPM Registry

    Tag->>WinJob: Trigger workflow
    WinJob->>DockerHub: Login
    WinJob->>WinJob: Setup Docker Buildx v3
    WinJob->>WinJob: Setup Go & fetch tags
    WinJob->>DockerHub: Build & push Windows images
    WinJob->>GitHub: Create Windows release artifacts
    
    WinJob->>MainJob: Dependency satisfied
    MainJob->>DockerHub: Login
    MainJob->>MainJob: Setup Docker Buildx v2
    MainJob->>MainJob: Setup Go & OSXCross
    MainJob->>DockerHub: Build & push Linux/Mac images
    MainJob->>GitHub: Create main release artifacts
    MainJob->>MainJob: Upload to CloudSmith & S3
    
    MainJob->>NPMJob: Dependency satisfied
    NPMJob->>NPMJob: Extract version & setup Node
    NPMJob->>NPM: Publish package
Loading

Additional Comments (1)

  1. .github/workflows/release_build_infisical_cli.yml, line 98 (link)

    logic: Inconsistent buildx versions - this job uses v2 while the Windows job uses v3. Should both be updated to v3 for consistency?

1 file reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

Copy link

@jerry7151053 jerry7151053 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants