Bump tauri-apps/tauri-action from 0 to 1

[dependabot]

Bumps tauri-apps/tauri-action from 0 to 1.

Release notes

Sourced from tauri-apps/tauri-action's releases.

action v1.0.0

[1.0.0]

• db4399e (#1194 by @​FabianLars) Breaking Change: .app.tar.gz & .app.tar.gz.sig files will now include the app version like all other bundles/installers.
• 53c8863 (#1315 by @​FabianLars) The download urls in latest.json will now use the github url instead of the browser download url.
• 9b64567 (#1167 by @​FabianLars) Breaking Change: Drop support for Tauri v1 and unstable v2 (alpha, beta, rc) versions.
• 9491f9d (#1177 by @​FabianLars) Breaking Change: The action will now fail if draft: true is set but the relevant release is not a draft.
• ab62863 (#1176 by @​FabianLars) The frontend lockfile detection will now move up the file tree to fix issues in workspaces.
• adb8bd3 (#1170 by @​FabianLars) Breaking Change: Remove includeRelease and includeDebug. You can switch to debug builds via args: --debug. To upload release and debug builds, run tauri-action twice, preferably in a job matrix for concurrent builds.
• eea1890 (#1175 by @​FabianLars) Improved runner detection to prevent silent fails if runner (npm, pnpm, yarn, bun) was not installed while a lockfile was present.
• acc588b (#1203 by @​FabianLars) Added initial Android & iOS support. This only includes building (=== running tauri android|ios build), installing dependencies and uploading to stores must be done manually.
• 2e37e06 (#1174 by @​FabianLars) Use npm exec instead of npm run if @tauri-apps/cli was detected with no tauri script in package.json.
• 1898cf4 (#1186 by @​FabianLars) Fiixed an issue that caused outdated signatures for macos universal builds in latest.json when re-running the action on the same release multiple times.
• 5c7403d (#1326 by @​FabianLars) Expose mainBinaryName in releaseAssetNamePattern and workflowArtifactNamePattern.
• 5d35c8e (#1189 by @​FabianLars) The upload release assets will now have the original file as its label which will show as the filename on the GitHub Release page and will be used internally to update assets on reruns and to get the download urls for latest.json
• c18827e (#1183 by @​FabianLars) Breaking Change: Renamed assetNamePattern to releaseAssetNamePattern.
• 766720b (#1172 by @​FabianLars) Breaking Change: Removed the feature to automatically initialize a Tauri project.
• 25f3730 (#1208 by @​FabianLars) Breaking Change: Renamed includeUpdaterJson to uploadUpdaterJson for consistency with other similar options.
• 53c8863 (#1315 by @​FabianLars) Removed Gitea support.
• 6d11c27 (#1185 by @​FabianLars) Breaking Change: Removed updaterJsonKeepUniversal. This is now always enabled.
• 7485c95 (#1169 by @​FabianLars) Switch from unmaintained @iarna/toml to smol-toml. No user-facing changes.
• 8236c82 (#1277 by @​FabianLars) Semi-Breaking Change: The action will now update the name and body of existing releases.
• 05c1b09 (#1178 by @​FabianLars) Added built-in variant of actions/upload-artifact to easily upload each bundle as a seperate archive. This may be removed once actions/upload-artifact#331 lands.
• 6434f9a (#1296 by @​Ludea) Added initial support for vite+.

action v0.6.2

[0.6.2]

• 73e111f (#1288) The action can now detect the workspace root correctly if the tauri project is configured as the cargo workspace root.

action v0.6.1

[0.6.1]

• ad5c271 (#1241 by @​FabianLars) Fixed an issue that caused the action to only read one --config arg.

action v0.6.0

[0.6.0]

• e918a06 (#1133) Encode tagName option value in latest.json URL.
• 45acc19 (#1164) Add generateReleaseNotes config to use GitHub's release notes API to auto generate the release name and/or body.
• 59a1a70 (#1166) Fix default file name pattern to match tauri's file names again.
• 08112f7 (#1106) Added experimental support for Gitea hosted instances.
• 08112f7 (#1106) Added a config to set the GitHub API URL which should help users with self-hosted instances and those using GitHub Enterprise.
• b067139 (#1130) The action now uses node v24 which raises the minimum GitHub runner version to v2.327.1.

action v0.5.25

... (truncated)

Changelog

Sourced from tauri-apps/tauri-action's changelog.

[0.5.21]

• 5666b68 (#1030 by @​997R8V10) retryAttempts is now also applied to uploads.

Commits

• 1deb371 Apply Version Updates From Current Changes (#1191)
• 35033cf chore(deps): update dependency @​vercel/ncc to v0.44.0 (#1323)
• 5ead4aa refactor: simplify createArtifact function (#1327)
• 7899682 ci: update actions (#1328)
• f201b79 chore(deps): update dependency @​types/node to v24.13.2 (#1320)
• 5c7403d feat: default naming scheme for mobile assets, closes #1317 (#1326)
• 71e781d chore(deps): update dependency @​biomejs/biome to v2.5.1 (#1318)
• f51677a chore(deps): update dependency smol-toml to v1.7.0 (#1324)
• 61337b4 chore(deps): update dependency @​types/node to v24.12.3 (#1316)
• 53c8863 refactor: Use github api as download url in latest.json (#1315)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

[greptile-apps]

Greptile Summary

This PR bumps tauri-apps/tauri-action from v0 to v1 in the release workflow for both macOS and Windows build steps.

• The version pin is updated in two places (build and publish macOS and build and publish Windows), but a breaking input rename from includeUpdaterJson → uploadUpdaterJson introduced in v1 is not addressed, leaving the updater-JSON suppression silently ignored.

Confidence Score: 3/5

The version bump itself is straightforward, but the workflow will misbehave on the first release run because the updater-JSON suppression no longer takes effect.

Both build steps pass includeUpdaterJson: false, which tauri-action v1 no longer recognises — it was renamed to uploadUpdaterJson. The old key is silently dropped, so each platform build will upload its own partial latest.json to the release. The custom publish-updater-json job does overwrite it at the end with --clobber, but the intermediate uploads are unintended and could cause problems on re-runs or if the final job fails before completing.

.github/workflows/release.yml — both includeUpdaterJson inputs need to be updated to uploadUpdaterJson.

Important Files Changed

Filename	Overview
.github/workflows/release.yml	Bumps tauri-action from v0 to v1 in both macOS and Windows build steps; the renamed includeUpdaterJson → uploadUpdaterJson input is not updated, so the updater-JSON suppression is silently ignored in v1.

Comments Outside Diff (2)

1. .github/workflows/release.yml, line 230-233 (link)

   The includeUpdaterJson input was renamed to uploadUpdaterJson in tauri-action v1 (see breaking change in PR notes). As written, the old key is silently ignored by the action, so the default value of uploadUpdaterJson (which is true) takes effect. This means both the macOS and Windows build steps will each upload their own platform-specific latest.json to the release — exactly what this workflow tries to prevent by generating a single combined updater JSON in the publish-updater-json job. The custom job does run last with --clobber, so the combined file eventually wins, but two intermediate redundant uploads will still occur (and could race on re-runs).

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: .github/workflows/release.yml
   Line: 230-233
   
   Comment:
   The `includeUpdaterJson` input was renamed to `uploadUpdaterJson` in tauri-action v1 (see breaking change in PR notes). As written, the old key is silently ignored by the action, so the default value of `uploadUpdaterJson` (which is `true`) takes effect. This means both the macOS and Windows build steps will each upload their own platform-specific `latest.json` to the release — exactly what this workflow tries to prevent by generating a single combined updater JSON in the `publish-updater-json` job. The custom job does run last with `--clobber`, so the combined file eventually wins, but two intermediate redundant uploads will still occur (and could race on re-runs).
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

2. .github/workflows/release.yml, line 260-263 (link)

   Same renamed input issue on the Windows step — includeUpdaterJson must be uploadUpdaterJson in tauri-action v1.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: .github/workflows/release.yml
   Line: 260-263
   
   Comment:
   Same renamed input issue on the Windows step — `includeUpdaterJson` must be `uploadUpdaterJson` in tauri-action v1.
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
.github/workflows/release.yml:230-233
The `includeUpdaterJson` input was renamed to `uploadUpdaterJson` in tauri-action v1 (see breaking change in PR notes). As written, the old key is silently ignored by the action, so the default value of `uploadUpdaterJson` (which is `true`) takes effect. This means both the macOS and Windows build steps will each upload their own platform-specific `latest.json` to the release — exactly what this workflow tries to prevent by generating a single combined updater JSON in the `publish-updater-json` job. The custom job does run last with `--clobber`, so the combined file eventually wins, but two intermediate redundant uploads will still occur (and could race on re-runs).

```suggestion
          uploadUpdaterJson: false
          args: ${{ matrix.tauri-args }}

      - name: build and publish Windows
```

### Issue 2 of 2
.github/workflows/release.yml:260-263
Same renamed input issue on the Windows step — `includeUpdaterJson` must be `uploadUpdaterJson` in tauri-action v1.

```suggestion
          uploadUpdaterJson: false
          args: ${{ matrix.tauri-args }}

  publish-updater-json:
```

_{Reviews (1): Last reviewed commit: "Bump tauri-apps/tauri-action from 0 to 1" | Re-trigger Greptile}