Use package version for Winget publish#594
Merged
sathvikkumar-octo merged 2 commits intomainfrom May 1, 2026
Merged
Conversation
The winget step previously derived the published version from Octopus.Release.Number. This breaks if the Octopus release name diverges from the package version (e.g. a 2.21.0-hotfix1 release containing octopus-cli@2.21.0). Source the version from the cli package metadata instead, so the published winget version always matches what's in the package being deployed. Adds a non-extracting cli package reference to the winget step to make PackageVersion available without unzipping the 66 MB package.
|
|
sathvikkumar-octo
force-pushed
the
sk/winget-version
branch
from
05f9821 to
b477c6c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Don't use
Octopus.Release.Numberfor the Winget push as it means if there is an error deploying the release we can't easily create a new release to try again and need to delete the old release first.This brings it inline with the other external repositories we are deploying the CLI to