Nope:
erlangen:~ # grep ^solver /etc/zypp/zypp.conf
solver.onlyRequires = true
solver.allowVendorChange = true
solver.dupAllowVendorChange = true
erlangen:~ #
Users may want to undo the restrictive default configuration and enable vendor change again. They call it “brute force”. However considerate usage of vendor change does away with most issues of distribution upgrade:
“Note that there can be some subtleties with updates, especially with multiple repositories. See for example recent discussion about using zypper dup versus zypper up and zypper dup priorities.”
https://en.opensuse.org/Portal:Tumbleweed
" zypper dup ensures that all installed packages come from one of the available repositories. It does not consider the version or architecture, but prevents changing the vendor of the installed packages by default, using the --no-allow-vendor-change option. If you have third-party repositories enabled, some repositories may break during the upgrade. In this case, use --allow-vendor-change instead."
The GUI updater relying on PackageKit and Yast2 use libzypp too. Some implementation details differ, e.g. The package glibc is essential to correct operation and cannot be removed using this tool - #41 by karlmistelberger. This warrants some extra fun Tumbleweed folks aren’t asking for.