You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building two .msi packages. One for Windows 11 & one for Windows 10, due to this when we go to publish the action creates a race condition and only uploads one of the two .msi packages (as they are the same name). An easy work around for this would be to be able to add a variable to the asset name such as "matrix.platform" or something along these lines.
My suggestion is to simply add assetName: as an option on the publish portion of the workflow.
The text was updated successfully, but these errors were encountered:
Unfortunately [it's not yet possible for Tauri](tauri-apps/tauri-action#215), nor there's any GH action for that, _but_ [there's an API endpoint](https://docs.github.com/en/rest/releases/assets#update-a-release-asset) we could use.
Since it's only the Tauri assets that are not according to the new standard, I think it's fine to keep it something we manually update, otherwise we can try to build a script that taps into that endpoint, later.
Building two .msi packages. One for Windows 11 & one for Windows 10, due to this when we go to publish the action creates a race condition and only uploads one of the two .msi packages (as they are the same name). An easy work around for this would be to be able to add a variable to the asset name such as "matrix.platform" or something along these lines.
My suggestion is to simply add
assetName:
as an option on the publish portion of the workflow.The text was updated successfully, but these errors were encountered: