Octopus Deployments api

HI Team,

we are working on a script to automate consolidated release notes for releases created in octopus,

we are doing it through this api

we wanted to know how octopus is calculating, the changes

Hi @chandramouli429,

Thanks for getting in touch!

There is a bit more detail on how the deployments notes are generated here, including how they differ for pre-release versions.

The short answer though is that Octopus is simply combining the releases notes of all versions between the release being deployed and the last successful release.


HI @paul.calvert,

thanks for quick response.

we are having three channels for a project.
Does octopus consider all the releases irrespective of the channels ??

It will only look at releases within the same channel.

HI @paul.calvert,

We are having three channels , with version rules
alpha (4.6)
beta (4.5)
gamma (4.4)

recently we have modified our version rules such that, we accept the below package versions
alpha (4.7)
beta (4.6)
gamma (4.5)

we have created a new release and deployed using beta channel (4.6).
Now when we pull the changes, it is taking releases from from alpha channel as well.

Is this expected??

Thanks in Advance

I will run some testing around this and let you know.

Can you confirm what version of Octopus you are currently running?

we are using v2020.3.1 version of octopus.

I’ve tested this out and discussed it internally, and this behaviour is intentional.

Previously, when I had tested this across channels, my additional channels had been using pre-release tags which excluded them from the deployment notes as detailed here: https://octopus.com/docs/releases/deployment-notes#Versioning

So, when constructing the deployment notes, Octopus will take into account any full version release within the project, regardless of which channel the release was created in.

Apologies for the incorrect information earlier.

1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.