Today we have upgraded our Octopus.Server to 3.6.1 and faced a major issue. Octopus doesn’t show packages in
latest section if it has pre-release tag:
Below are all versions of the package:
I assume this issue is related to this task on github: Create Release is including pre-release versions for Latest.
I’ve made a little research and found that Web-app makes an API-request to URL
OCTOPUS/api/feeds/feeds-builtin/packages?packageId=graphite-powershell-functions&partialMatch=false&includeMultipleVersions=true&includeNotes=false&includePreRelease=false&take=1 and Octopus.Server responses with zero-length array. If I change option
includePreRelease to true it returns package normally.
It seems also, this issue is only reproduced in Web-App but neither in teamcity nor console client.
I would be very appreciated if you solve this issue as soon as possible.
I have an insight! I think this issue is related to channels. In issue Create Release is including pre-release versions for Latest you hided pre-release packages from channels if that channel doesn’t include pre-release packages. This is right behavior, but this behavior should not influence to default channel.
I came here to report this same issue.
I can confirm that it affects us in the same way as the Denis describes. Web interface & Pre-release packages only are affected.
It only started happening after upgrading to 3.6.0. We are now on 3.7.1 but the problem persists.
In #2872 we updated the Latest column to exclude pre-release packages by default (same behaviour as pre-Channels) as the help text on the column specifically said this was the expected behaviour. After further feedback from customers and discussions within the team we have concluded we implemented the incorrect solution here, so we’ve raised #2991 to correct this as soon as possible.
My sincere apologies for the inconvenience caused by this.
Thank you for information. I will stay in touch.
Would you mind me asking whether there are any news? A week has passed but ticket is still open. This issue causes inconvenience as we have to manually choose every package when release is created.
Is there any chance to solve this issue in the near future?
Thank you in advance!
No news at this time I’m afraid, it’s in the queue but as we’re heading into the Christmas and New Year holidays it might not be until the new year that this bug is actioned.
My apologies for the inconvenience caused by this issue.
Thank you and warm regards,
I don’t lose hope it could be solved before New Year Anyway, thank you for information
This is also a big issue for us. Are there any release plans to change it back again
The fix for this will be released in
3.7.13 which should go out in the next few hours.