Skip to content

Commit 96f65fe

Browse files
authored
fix(bundler): Fix updater bundler warning condition for v2 artifacts (#10188)
1 parent 11aa774 commit 96f65fe

2 files changed

Lines changed: 7 additions & 2 deletions

File tree

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
tauri-bundler: patch:bug
3+
---
4+
5+
On macOS, the bundler will now correctly print a warning when the updater is enabled while the `.app` bundle is disabled.

tooling/bundler/src/bundle.rs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -161,8 +161,8 @@ pub fn bundle_project(settings: &Settings) -> crate::Result<Vec<Bundle>> {
161161
package_type: PackageType::Updater,
162162
bundle_paths: updater_paths,
163163
});
164-
} else if updater.v1_compatible {
165-
log::warn!("The updater bundle target exists but couldn't find any updater-enabled target, so the updater artifacts won't be generated. Please add one of these targets as well: app, appimage, msi, nsis");
164+
} else {
165+
log::warn!("The bundler was configured to create updater artifacts but no updater-enabled targets were built. Please enable one of these targets: app, appimage, msi, nsis");
166166
}
167167
if updater.v1_compatible {
168168
log::warn!("Legacy v1 compatible updater is deprecated and will be removed in v3, change bundle > createUpdaterArtifacts to true when your users are updated to the version with v2 updater plugin");

0 commit comments

Comments
 (0)