The set-output command is deprecated and will be disabled soon.

[anuteresa]

No description provided.

[lfg-will]

+1. This is causing the following annotation to show for any jobs using this action:

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

[summitt]

+1 . Would be great if there could be a fix for this soon.

[timam]

+1

[vitalykarasik]

I created #82

[kevin-riquena]

+1

[jefflaporte]

@ebinmore Would you be able to merge #82 from @vitalykarasik ?

[CSHawley]

Just a reminder that Slack Send exists as an alternative. It looks to be developed in-house by the Slack team.

[vitalykarasik]

Just a reminder that Slack Send exists as an alternative. It looks to be developed in-house by the Slack team.

You're right, but I prefer this plugin because I don't need to generate the whole notification's body, so I need less code in my workflow. (BTW, during migration from Jenkins to GHA I compared a few Slack plugins and couldn't find 'my ideal plugin'. For example, in this one, I lack the ability to add a custom body. A few others don't support modern Slack integration. )

[aldenquimby]

This repo appears abandoned: #69 (comment)

@klamas1 would you be willing to merge and ship #82 and take over as the primary fork for this repo moving forward?

[klamas1]

@klamas1 would you be willing to merge and ship #82 and take over as the primary fork for this repo moving forward?

Unfortunately, I rarely use github actions, so I won't be able to keep the fork up to date and timely update the versions

[justinr636]

@aldenquimby I can't commit to any further maintenance, but I have taken the changes from @vitalykarasik in PR #82, forked the code, and published it to a new marketplace action found here: https://github.com/marketplace/actions/gha-slack-notify-build

[vitalykarasik]

Dear All - thanks!
I'm using this plugin and I'll be happy to host a fork, but - I'm DevOps, not a developer. My JS skills are close to zero. So I have no problem testing suggested PRs and merge, but it's all that I know.

[rmagri]

+1