Describe the bug
I have the 25.0.0 version of the custom device with VeriStand 2024 support installed. When I go to install the 25.0.1 patch to fix Auto-Detect Modules, I get an error that the package cannot be installed.
To Reproduce
Steps to reproduce the behavior:
- Download and install the 25.0.0 release (
ni-scan-engine-veristand-<version>-support_25.0.0.8_windows_x64.nipkg)
- Download and attempt to install the 25.0.1 release (
ni-scan-engine-veristand-<version>-support_25.0.1.2_windows_x64.nipkg)
- See the NIPM error about a newer version being already installed
Expected behavior
I would expect 25.0.1 to upgrade 25.0.0.
Screenshots
Workaround
Manually uninstall the 25.0.0.8 package in NIPM before installing 25.0.1.2.
Additional context
The issue is due to the releaseVersion in the pipeline config file not getting incremented in the release branch. Because the build numbers are incremented per branch build history, the package that was named 25.0.1.2 actually contains Version: 25.0.0.2 in the control file, which is older than the 25.0.0.8 version in the 25.0.0 release file.
Describe the bug
I have the 25.0.0 version of the custom device with VeriStand 2024 support installed. When I go to install the 25.0.1 patch to fix
Auto-Detect Modules, I get an error that the package cannot be installed.To Reproduce
Steps to reproduce the behavior:
ni-scan-engine-veristand-<version>-support_25.0.0.8_windows_x64.nipkg)ni-scan-engine-veristand-<version>-support_25.0.1.2_windows_x64.nipkg)Expected behavior
I would expect 25.0.1 to upgrade 25.0.0.
Screenshots
Workaround
Manually uninstall the
25.0.0.8package in NIPM before installing25.0.1.2.Additional context
The issue is due to the
releaseVersionin the pipeline config file not getting incremented in the release branch. Because the build numbers are incremented per branch build history, the package that was named25.0.1.2actually containsVersion: 25.0.0.2in the control file, which is older than the25.0.0.8version in the 25.0.0 release file.