Hi Dennis, thanks for the additional information, that use case makes a lot of sense and we’re looking into what we might be able to do to support it.
As I mentioned, we’ve been doing a lot of work in this area recently and updating all of our build server plugins to support some new features for getting build/package metadata into Octopus. The Azure DevOps changes for that are almost complete and should be shipping fairly soon. We’d most likely be looking to deprecate the existing functionality at that point and probably implement support for this feature in the new Package Metadata step. One of the advantages of this is that the release note information is tied to the package you built and not the release you created. So say you had to create another release using the same packages versions for some reason, you would get the same release note details because they are coming with the package(s). Another scenario might be if your build process consisted of multiple packages, each could have it’s own markdown file in the source code and you add the Package Metadata step for each package, then you get a many to one between release notes and a release.
I hope that makes sense, if you have any questions please let me know and please check out the new step features once they are release and let us know what you think.