v2.2.2

Bump path-parse from 1.0.6 to 1.0.7 (#26)

Bumps [path-parse](https://github.com/jbgutierrez/path-parse) from 1.0.6 to 1.0.7.
- [Release notes](https://github.com/jbgutierrez/path-parse/releases)
- [Commits](https://github.com/jbgutierrez/path-parse/commits/v1.0.7)

---
updated-dependencies:
- dependency-name: path-parse
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

v2.2.1

Readme update and sample updates to support Windows runners (https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners)

v2.2.0

• Added a rudimentary support for updating posted messages (see .github/workflows/slack-update-message.yml)
• Dependency updates

v2.1.0

Dependency updates

No new features :)

Dependencies

• @actions/github latest 4.0.0 ❯ 5.0.0

DevDependencies

• @vercel/ncc latest 0.26.2 ❯ 0.28.6
• eslint latest 7.19.0 ❯ 7.27.0
• eslint-config-prettier latest 7.2.0 ❯ 8.3.0
• eslint-plugin-prettier latest 3.3.1 ❯ 3.4.0
• jest latest 26.6.3 ❯ 27.0.3
• prettier latest 2.2.1 ❯ 2.3.0

v2.0.1

Added sample action and updated readme on how to send thread responses

v2.0.0

What's new

• Added support for sending reactions on messages (https://api.slack.com/methods/reactions.add)

• Improved output from the action. It's now a plain json string (not wrapped in an array) with a response object, that contains all the things you need if you are later going to send a reaction to the message

{
  "statusCode": 200,
  "statusMessage": "OK",
  "ok": true,
  "result": "<deprecated - same as response but as string>",
  "response": {
    "ok": true,
    "channel": "XXXX",
    "ts": "1612623790.009600",
    "message": {
      "type": "message",
      "subtype": "bot_message",
      "text": "Lipsum",
      "ts": "1612623790.009600",
      "username": "Lipsum",
      "bot_id": "XXXX"
    }
  }
} 

• Improved way of reporting errors to action runner

Breaking change

This is only important if you are parsing the result from the action

In v1.x there was a bug, that made the result of the action to be wrapped in an array. This made it hard to parse and to use the result from the action. Luckily the majority didn't care about the result :) .

But if you have a script the parse the slack-result, please use something like this to get the json values:

run: echo "${{ steps.send-message.outputs.slack-result }}"

or

run: echo "${{ fromJson(steps.send-message.outputs.slack-result).response.channel }}"

(See https://github.com/archive/github-actions-slack/blob/v2.0.0/.github/workflows/slack-reaction.yml)

v1.1.0

• Changed ncc to @vercel/ncc

• Upgrade of all dependencies

• Small cleanups and readme improvements

v1.0.4

#9

v1.0.3

#6

v1.0.2

Small fix in Github Action definition file (no impact)