Revert breaking change on new line

[VincentLanglet]

ℹ️ About

Hi @JoshCoady, the PR #9 introduce by @denis-trofimov was a breaking change:

• As shown by the failing test in update test to work with changes from #9 #12
• As reported by @bachiri here update test to work with changes from #9 #12 (comment)
• As reported by @hasier feat: Add input variable to stringify result #15

I encountered this breaking change, bumping from 1.0.1 to 1.0.2 give the result:

• from

- to

By escaping the \n they are not correctly interpreted by Slack anymore.

This is my github actions:

            -   name: Convert changelog's Markdown to mrkdwn
                id: changelog
                uses: LoveToKnow/[email protected]
                with:
                    text: ${{ github.event.release.body }}

            -   name: Post to a Slack channel
                id: slack
                uses: slackapi/[email protected]
                with:
                    channel-id: 'deploy'
                    payload: | 
                        {
                            "blocks": [
                        		{
                                    "type": "header",
                                    "text": {
                                        "type": "plain_text",
                                        "text": "A new version has been deployed to prod! Make the world a better place!"
                                    }
                                },
                                {
                                    "type": "section",
                                    "text": {
                                        "type": "mrkdwn",
                                        "text": ${{ toJSON(steps.changelog.outputs.text) }}
                                    }
                                }
                            ]
                        }

I agree with @hasier the right way is to Jsonify the payload, this is what we were doing.

• You can do it, manually in the github actions toJSON
• You can do it inside the lib with an option like feat: Add input variable to stringify result #15

I would say that @denis-trofimov missed this part, his PR manually escape the \n character cause he had trouble with, but the same issue could occur with some other character and not, the github actions leave us with a broken state where

• Using toJSON break the \n
• Not using toJson break with some other character we need to escape

I let

mrkdwn.replace(/\r\n|\r|\n/g, "\n");

to use the correct line delimiter, because I think it still can be an improvement ; but I removed the escaping.

Thanks

• Has 🧪 tests
• Has 📖 documentation

• 🎫 Related Ticket

[github-actions]

🎉 This PR is included in version 1.1.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀