Some Valid Versioning usage in External Feeds (GitHub Nuget) will result in Package Not Found in Feed #6817
Closed
5 tasks done
Labels
area/core
feature/feeds
kind/bug
This issue represents a verified problem we are committed to solving
Prerequisites
The bug
Using a GitHub Nuget external feed, some versioning will result in The package was not found in the feed. An example of this is
#.#.#-AAA-####-AAAAA-AAAAA.###
. This versioning is valid semver, but Octopus fails to pull in the details of the package on the release page. However, the package still deploys correctly. I would expect this behavior is not limited to GitHub Nuget feeds, but that is what I discovered and tested it on.What I expected to happen
I would expect the release page to be able to find the package and get the information.
Steps to reproduce
Screen capture
Affected versions
Octopus Server: Latest at time of writing (2021.1.6460)
Workarounds
Change the versioning schema of your package or ignore the error, as the package will still deploy correctly.
Links
Source Ticket: https://help.octopus.com/t/the-package-was-not-found-in-the-feed/26423/3
Internal Slack Convo: https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1616089126042000
Internal Cloud Repro: https://octopus-operations.octopus.app/app#/Spaces-83/projects/github-nuget-feed-tests/deployments/releases/0.0.1
Additional Ticket: https://octopus.zendesk.com/agent/tickets/71812
The text was updated successfully, but these errors were encountered: