Octopus "No package version was found in the feed" in CI
When create-release lets Octopus auto-select the latest package, the server searched the feed and found nothing matching the package ID and any channel version rules. The feed is empty for that package, the ID differs, or a channel filter excludes every candidate.
What this error means
octo create-release fails with "Could not find any packages" or "No package version was found in the feed for step X" when relying on latest-package selection.
octo create-release --project "Web"
Could not find any packages with the id 'Web' in the feed 'Octopus Server (built-in)'.Common causes
The feed has no package with that ID
The package was pushed under a different ID, or never pushed, so latest-selection finds nothing to bind.
A channel version rule excludes all versions
The active channel restricts versions with a rule (for example a pre-release tag filter) that no pushed package satisfies.
How to fix it
Confirm the package ID and feed
- List packages in the feed to see the exact IDs present.
- Match the deployment step package ID to what was pushed.
- Re-run create-release so latest-selection finds a candidate.
octo push --package "Web.1.0.0.zip" --server "$OCTOPUS_URL" --apiKey "$OCTOPUS_API_KEY"
octo create-release --project "Web" --server "$OCTOPUS_URL" --apiKey "$OCTOPUS_API_KEY"Relax or match the channel version rules
If a channel filter excludes your versions, deploy through a channel whose version rules accept the pushed package, or adjust the rule.
octo create-release --project "Web" --channel "Default" \
--server "$OCTOPUS_URL" --apiKey "$OCTOPUS_API_KEY"How to prevent it
- Keep package IDs identical between push and deployment steps.
- Verify channel version rules match the versions your build produces.
- Push the package before running create-release with latest-selection.