Description
This task aims to improve the existing SDK publication GitHub Action workflow for both 'next' and 'latest' versions. The primary goal is to implement a robust error notification system to Slack whenever a publication fails. Additionally, a new manual trigger option needs to be added to the GitHub Workflow specifically for generating and publishing a new 'next' tag version.
Acceptance Criteria
Upon any failure in the SDK publication workflow (for both 'next' and 'latest' versions), a notification must be sent to a designated Slack channel.,Each Slack error notification must include a direct link to the Pull Request that triggered the action.,Each Slack error notification must include a direct link to the specific GitHub Action run, allowing for easy diagnosis of what went wrong.,The GitHub Workflow must be updated to include a new manual trigger option, likely labeled 'next' or similar, enabling the creation and publication of a new 'next' version of the SDK tag.,The newly added manual 'next' trigger option must successfully generate and publish the 'next' SDK version when executed.
Priority
Medium
Additional Context
Currently, the 'next' tag for the SDKs is only generated automatically upon merging a Pull Request. If this publication process fails, there is no reliable way to re-run it effectively. The 'Run-again' option often does not pick up changes or fixes made to address the issue, leading to difficulties in deploying a corrected 'next' version. The introduction of a manual 'next' tag generation option is crucial to overcome this limitation and ensure successful re-runs when needed.
Description
This task aims to improve the existing SDK publication GitHub Action workflow for both 'next' and 'latest' versions. The primary goal is to implement a robust error notification system to Slack whenever a publication fails. Additionally, a new manual trigger option needs to be added to the GitHub Workflow specifically for generating and publishing a new 'next' tag version.
Acceptance Criteria
Upon any failure in the SDK publication workflow (for both 'next' and 'latest' versions), a notification must be sent to a designated Slack channel.,Each Slack error notification must include a direct link to the Pull Request that triggered the action.,Each Slack error notification must include a direct link to the specific GitHub Action run, allowing for easy diagnosis of what went wrong.,The GitHub Workflow must be updated to include a new manual trigger option, likely labeled 'next' or similar, enabling the creation and publication of a new 'next' version of the SDK tag.,The newly added manual 'next' trigger option must successfully generate and publish the 'next' SDK version when executed.
Priority
Medium
Additional Context
Currently, the 'next' tag for the SDKs is only generated automatically upon merging a Pull Request. If this publication process fails, there is no reliable way to re-run it effectively. The 'Run-again' option often does not pick up changes or fixes made to address the issue, leading to difficulties in deploying a corrected 'next' version. The introduction of a manual 'next' tag generation option is crucial to overcome this limitation and ensure successful re-runs when needed.