Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrading the
circleci/slackorb to version 6.0.0 introduces a breaking change that will cause theslack-on-failcommand to fail.In v6.0.0, the
customparameter of theslack/notifycommand no longer accepts a raw JSON string. Instead, it requires a path to a file containing the JSON payload.To fix this, you need to modify the
slack-on-failcommand (defined on lines 17-95) to first write the custom JSON payload to a file, and then pass the path to that file to theslack/notifycommand.Here is an example of how you could modify the
stepsin theslack-on-failcommand:This change preserves the
install curlstep, adds a new step to create the JSON template file, and updates theslack/notifycall to use this file. The emptytextfield from the original JSON has been removed as it's not necessary when usingblocks.