Slack Message is doesn't triggered from Manual SDK Release
Open
A pull request for this has already been merged.
- #35461 by @KevinDavilaDotCMS — merged
OKR : Customer Support
stale
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
When a developer triggers a Manual SDK Release using the Github Workflow, the slack message is doesn't sent to the log-channel.
This can cause some confusions and made lost the flow of versions
Steps to Reproduce
- Trigger a Manual SDK Release
- See the new version is deployed but the message on slack never comes
Acceptance Criteria
- After trigger the Manual SDK Release, the slack message is send to the proper channel
dotCMS Version
latest
Severity
Low - Minor issue or cosmetic
Links
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the GitHub Workflow that handles the Manual SDK Release and compare its Slack notification step with other release paths. Reproduce a manual release and verify that the expected message reaches the linked log channel; the merged pull request should also be checked for the current status of the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100