From 3ec372c176ff0dca6f708dccd869e8b5ada87f7b Mon Sep 17 00:00:00 2001 From: "Dustin L. Howett" Date: Wed, 28 Jan 2026 12:27:05 -0600 Subject: [PATCH] vpack: ensure that we put the right version number in (#19793) I just submitted a vpack to Windows and it turned out to be version "0.0.5". Whoops. --- .../templates-v2/pipeline-onebranch-full-release-build.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/build/pipelines/templates-v2/pipeline-onebranch-full-release-build.yml b/build/pipelines/templates-v2/pipeline-onebranch-full-release-build.yml index 0ddc339293..20a92caaea 100644 --- a/build/pipelines/templates-v2/pipeline-onebranch-full-release-build.yml +++ b/build/pipelines/templates-v2/pipeline-onebranch-full-release-build.yml @@ -210,6 +210,8 @@ extends: ob_createvpack_taskLogVerbosity: Detailed ob_createvpack_verbose: true ob_createvpack_vpackdirectory: '$(JobOutputDirectory)\vpack' + ob_createvpack_versionAs: string + ob_createvpack_version: '$(XES_APPXMANIFESTVERSION)' ob_updateOSManifest_gitcheckinConfigPath: '$(Build.SourcesDirectory)\build\config\GitCheckin.json' # We're skipping the 'fetch' part of the OneBranch rules, but that doesn't mean # that it doesn't expect to have downloaded a manifest directly to some 'destination'