.goreleaser.yml

project_name: SatisfactoryModManager

before:
  hooks:
    - go generate -x -tags tools ./...
    - go mod tidy
    - ./.github/convertWailsJsonPaths.sh

    # Apparently only wails build generates the embedded directory
    - mkdir -p frontend/build
    - touch frontend/build/.gitkeep

    - wails generate module
    - pnpm -C frontend install
    - pnpm -C frontend build

### Build

builds:
  - id: standalone

    goos:
      - linux
    goarch:
      - amd64

    # Wails v2 apps cannot be built using regular go build, and must use wails build
    # However, wails takes only the filename as the -o argument, so we use a wrapper that handles that
    gobinary: "./.github/wailsWrapper.sh"
    ldflags:
      # The default args
      - -s -w -X main.version={{.Version}} -X main.commit={{.Commit}} -X main.date={{.Date}}
      # Auto-update mode
      - -X main.updateMode=standalone

    flags:
      - -s
      - -skipbindings

  
  - id: package-manager

    goos:
      - linux
    goarch:
      - amd64

    # Wails v2 apps cannot be built using regular go build, and must use wails build
    # However, wails takes only the filename as the -o argument, so we use a wrapper that handles that
    gobinary: "./.github/wailsWrapper.sh"
    ldflags:
      # The default args
      - -s -w -X main.version={{.Version}} -X main.commit={{.Commit}} -X main.date={{.Date}}
      # Auto-update mode
      - -X main.updateMode=package-manager

    flags:
      - -s
      - -skipbindings

  - id: nsis

    binary: SatisfactoryModManager-Setup # This name must match the nsis script OutFile, so the installer overwrites the wails built exe

    goos:
      - windows
    goarch:
      - amd64

    # Wails v2 apps cannot be built using regular go build, and must use wails build
    # However, wails takes only the filename as the -o argument, so we use a wrapper that handles that
    gobinary: "./.github/wailsWrapper.sh"
    ldflags:
      # The default args
      - -s -w -X main.version={{.Version}} -X main.commit={{.Commit}} -X main.date={{.Date}}
      # Auto-update mode
      - -X autoupdate.updateMode=nsis

    flags:
      - -s
      - -skipbindings
      - -nsis

### Package

archives:
  - id: windows-nsis
    builds:
      - nsis
    format: binary
    name_template: SatisfactoryModManager-Setup

  - id: standalone
    builds:
      - standalone
    format: binary
    name_template: "{{ .ProjectName }}_{{ .Os }}_{{ .Arch }}{{ with .Arm }}v{{ . }}{{ end }}{{ with .Mips }}_{{ . }}{{ end }}"

checksum:
  name_template: 'checksums.txt'

### Release

snapshot:
  name_template: '{{ .Version }}+{{ if ne .Branch "master" }}{{ .Branch }}.{{ end }}{{ .ShortCommit }}'

release:  
  draft: true
  name_template: "{{.ProjectName}} v{{.Version}}"
  
  # Include all artifacts: windows-nsis, standalone

  header: |
    ## Installation
    Download and run `SatisfactoryModManager-Setup.exe` (Windows) or `SatisfactoryModManager_linux_win64` (Linux)
    If you already have Satisfactory Mod Manager installed, you don't need to download it again, it will auto-update.