Going forward, start-release will be triggered from tags pushed by the build job, where the build job will create a tag on each run against next and will only increment the app version when it detects that the current app_version has already been released
To accompany the changes to the build job, I'm making the following updates to start-release
Create a new release notes file for the current app_version from unreleased.md if doesn't exist, otherwise, append unreleased.md to the existing file
Do not open a next --> main PR if one is already open
Update build_docs_from_html to check if the newly built readme differs from the previous readme to prevent empty commits from created
Stop generating headers in the markdown release notes for Splunkbase but keep them in the html release notes for Phantom Portal
Notes
nextand will only increment the app version when it detects that the currentapp_versionhas already been releasedapp_versionfromunreleased.mdif doesn't exist, otherwise, appendunreleased.mdto the existing filebuild_docs_from_htmlto check if the newly built readme differs from the previous readme to prevent empty commits from createdTesting