Setup Slack plugin for auto to notify on new CLI releases

[ghengeveld]

This adds the Slack plugin for auto so it will send a webhook notification to our Slack whenever a new CLI version is released. The SLACK_WEBHOOK_URL secret has been setup for this repository.

📦 Published PR as canary version: 11.4.1--canary.990.9191631016.0

✨ Test out this PR locally via:

npm install chromatic@11.4.1--canary.990.9191631016.0
# or 
yarn add chromatic@11.4.1--canary.990.9191631016.0

[ethriel3695]

@ghengeveld is the atTarget the slack channel or the group being pinged?

If it's the slack channel, we should do co-empathy

[ghengeveld]

@ethriel3695 It's the at-mention target, so that the team gets pinged. The default is @channel which I don't think is desirable. The target channel is configured through the Slack app config.

[ethriel3695]

This looks great to me.
All my questions have been answered as well.

Thanks @ghengeveld !

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 764456e1	✅ ∅ (target: 80.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (764456e)	Report Missing	Report Missing	Report Missing
Head commit (d5c9e61)	8471	6675	78.80%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#990)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy will stop sending the deprecated coverage status from June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩