<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=322016) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal **Slack notifications are incredibly helpful, and for us they shine particularly brightly when something has deployed or been published. Deployment is easy, publish is not.** For deployments, setting up the Slack integration to send a message is easy: just tick the Deployment box. For packages, such as NPM, our pipelines are set up to publish new packages upon tagging. The tag triggers a new pipeline which eventually gets to the publish job. We can notify a Slack channel upon tag, but not upon publish—therefore, the new package isn't actually available until the pipeline finishes. ### Related I found several issues and epics which appear related to this, though none explicitly mention package publish. * https://gitlab.com/gitlab-org/gitlab/-/issues/15516 - More options for event types on Slack integration * https://gitlab.com/groups/gitlab-org/-/epics/5238 - Fine-grained Slack notifications * https://gitlab.com/groups/gitlab-org/-/epics/936 - Slack Integration ### etc. I work for an Ultimate customer and we are in the process of moving all our NPM and Maven packages into the GitLab registry.