build(ci): upgrade tauri-apps/tauri-action to v1

[TimeToBuildBob]

Upgrades tauri-apps/tauri-action from v0 to v1 across build.yml and release.yml, and fixes a breaking-change parameter rename in release.yml.

Changes

• build.yml: tauri-action@v0 → tauri-action@v1
• release.yml: tauri-action@v0 → tauri-action@v1, includeUpdaterJson → uploadUpdaterJson

Why the parameter rename matters

includeUpdaterJson was renamed to uploadUpdaterJson in v1 (changelog). Without this fix, the old name is silently ignored and updater JSON is never uploaded for signed builds, breaking auto-update functionality.

Relation to #230

Dependabot PR #230 bumped the version pin but missed the parameter rename. This PR supersedes it with the complete migration.

[greptile-apps]

Greptile Summary

The PR completes the tauri-action v1 migration and adjusts release behavior for compatibility.

• Upgrades tauri-apps/tauri-action from v0 to v1 in build and release workflows.
• Renames includeUpdaterJson to the v1-compatible uploadUpdaterJson input.
• Sets releases to non-draft so reruns can reuse already-published releases.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains; the current configuration reuses existing published releases and resolves the previously reported rerun failure.

Important Files Changed

Filename	Overview
.github/workflows/build.yml	Upgrades the build step to tauri-action v1 without changing its existing inputs or build flow.
.github/workflows/release.yml	Completes the v1 input migration and fixes the previously reported published-release rerun failure by setting releaseDraft to false.

_{Reviews (2): Last reviewed commit: "fix(ci): set releaseDraft: false to avoi..." | Re-trigger Greptile}

[greptile-apps]

Published release reruns fail

When this workflow is rerun or manually dispatched for a tag whose release is already published, tauri-action v1 rejects that release because releaseDraft is true and then attempts to create a duplicate, causing the release workflow to fail.

[TimeToBuildBob]

Addressing the Greptile 4/5 finding on releaseDraft: true:

The concern is valid — tauri-action v1 enforces that releaseDraft: true invocations can only attach assets to a draft release, not a published one. This means reruns of failed matrix jobs would break if the draft had already been published.

However, the alternative (releaseDraft: false) auto-publishes immediately, removing the draft-review window that lets maintainers verify assets before making the release public.

The practical mitigation: if any matrix job fails, rerun it before manually publishing the draft. This keeps the normal workflow intact and avoids the edge case. Given that rerunning against an already-published release isn't part of the standard release process here, this limitation is acceptable.

If this becomes a real pain point in practice, the fix would be to split the workflow into two phases: a build phase that uploads artifacts to a staging area, and a separate publish step that only creates/updates the GitHub release — but that's a larger rework for another day.

[TimeToBuildBob]

@greptileai review

[TimeToBuildBob]

Greptile re-reviewed at 5/5 and all CI checks are green. Ready for maintainer merge.

[TimeToBuildBob]

CI-green and mergeable (Greptile 5/5) — waiting only on a maintainer click.

This PR is ready to merge, but the bot has pull-only access to this repo and can't self-merge — surfacing it here so it isn't lost. The monitoring loop will stop re-flagging it now that this note is posted.