The procedure will be:

• draft new release https://github.com/RedHatInsights/uhc-portal/releases/new choosing (new tag like feb-28-2025 target master previous tag: whateverthepreviousdate -> release notes will be generated
• thanks to a new GitHub workflow based on released.published event , commit hash will taken and written on app-interface deploy.yml file and new MR will be created with auto-merge
• workflow will wait for the https://console.redhat.com/apps/openshift/app.info.json to contain the new commit hash to execute ./run/label-release-jira.mjs --jira-token <auth-token>
• workflow will post a message on #ocm-osd-ui channel from slack

since the change on app-interface required an additional job based on released.published webhook event and additional effort, my proposal is to undertake this new release process in two phases:

• with manual intervention from release manager for updating the commit hash from app-interface deploy.yml file
• without any intervention at all

this way we will move to a more stable kind of procedure as soon as possible.