Skip to content

Make release automation validate existing tags and releases before publish #8

Description

@postigodev

Summary

The current PowerShell release flow already automates version sync, Tauri build, and GitHub release creation, but it should be more defensive around tag/release state.

Why this matters

We already hit a case where a local tag conflicted with GitHub release creation.

Expected outcome

Before publish, the script should validate things like:

  • target tag already exists locally
  • target tag already exists remotely
  • release already exists on GitHub
  • repo has uncommitted changes that would make the release inconsistent

Likely files

  • release.ps1

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or incorrectdevopsRelease, automation, or build pipeline workhelp wantedMaintainer would welcome contribution here

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions