chore(release): tag version 1.27.1

This commit is contained in:
@zimeg
2024-11-14 12:18:11 -08:00
parent bd0e2818bf
commit 74ae656892
10 changed files with 22 additions and 22 deletions
+12 -12
View File
@@ -52,7 +52,7 @@ Add this Action as a [step][job-step] to your project's GitHub Action Workflow f
```yaml
- name: Send GitHub Action trigger data to Slack workflow
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
payload-delimiter: "_"
env:
@@ -64,7 +64,7 @@ or
```yaml
- name: Send custom JSON data to Slack workflow
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
# This data can be any valid JSON from a previous step in the GitHub Action
payload: |
@@ -83,7 +83,7 @@ or
```yaml
- name: Send custom JSON data to Slack workflow
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
payload-file-path: "./payload-slack-content.json"
env:
@@ -97,7 +97,7 @@ or
```yaml
- name: Send custom JSON data to Slack workflow
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
payload-file-path: "./payload-slack-content.json"
payload-file-path-parsed: false
@@ -124,7 +124,7 @@ Add this Action as a [step][job-step] to your project's GitHub Action Workflow f
```yaml
- name: Post to a Slack channel
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
# Slack channel id, channel name, or user id to post message.
# See also: https://api.slack.com/methods/chat.postMessage#channels
@@ -141,7 +141,7 @@ Using JSON payload for constructing a message is also available:
```yaml
- name: Post to a Slack channel
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
# Slack channel id, channel name, or user id to post message.
# See also: https://api.slack.com/methods/chat.postMessage#channels
@@ -172,7 +172,7 @@ Please note that **the message update step does not accept a channel name.** Set
```yaml
- id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
# The following message update step does not accept a channel name.
# Setting a channel ID here for consistency is highly recommended.
@@ -196,7 +196,7 @@ Please note that **the message update step does not accept a channel name.** Set
}
env:
SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
- uses: slackapi/[email protected].0
- uses: slackapi/[email protected].1
with:
# Unlike the step posting a new message, this step does not accept a channel name.
# Please use a channel ID, not a name here.
@@ -231,7 +231,7 @@ Please note that **reply to a message does not accept a channel name.** Set a ch
```yaml
- id: deployment_message
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
channel-id: "CHANNEL_ID"
payload: |
@@ -240,7 +240,7 @@ Please note that **reply to a message does not accept a channel name.** Set a ch
}
env:
SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
- uses: slackapi/[email protected].0
- uses: slackapi/[email protected].1
with:
# Unlike the step posting a new message, this step does not accept a channel name.
# Please use a channel ID, not a name here.
@@ -273,7 +273,7 @@ Incoming Webhooks conform to the same rules and functionality as any of Slack's
```yaml
- name: Send custom JSON data to Slack workflow
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
# For posting a rich message using Block Kit
payload: |
@@ -301,7 +301,7 @@ If you need to use a proxy to connect with Slack, you can use the `HTTPS_PROXY`
```yaml
- name: Post to a Slack channel via a proxy
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
channel-id: 'CHANNEL_ID'
slack-message: 'This message was sent through a proxy'
@@ -7,7 +7,7 @@ jobs:
steps:
- name: Send GitHub trigger payload to Slack Workflow Builder
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
payload: |
{
@@ -7,7 +7,7 @@ jobs:
steps:
- name: Send GitHub trigger payload to Slack Workflow Builder
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
payload-file-path: "./example-workflows/Technique_1_Slack_Workflow_Builder/payloads/example.json"
env:
@@ -7,6 +7,6 @@ jobs:
steps:
- name: Send GitHub trigger payload to Slack Workflow Builder
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
@@ -7,7 +7,7 @@ jobs:
steps:
- name: Send GitHub trigger payload to Slack Workflow Builder
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
channel-id: 'SLACK_CHANNEL_ID' # ID of Slack Channel you want to post to
payload: |
@@ -7,7 +7,7 @@ jobs:
steps:
- name: Send GitHub trigger payload to Slack Workflow Builder
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
channel-id: 'SLACK_CHANNEL_ID' # ID of Slack Channel you want to post to
payload: "{\"text\": \"posting from a github action\"}"
@@ -7,7 +7,7 @@ jobs:
steps:
- name: Publish to slack channel via bot token
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
channel-id: 'SLACK_CHANNEL_ID' # ID of Slack Channel you want to post to
slack-message: 'posting from a github action!' # The message you want to post
@@ -7,7 +7,7 @@ jobs:
steps:
- name: Send GitHub trigger payload to Slack Workflow Builder
id: slack
uses: slackapi/[email protected].0
uses: slackapi/[email protected].1
with:
payload: |
{
+2 -2
View File
@@ -1,12 +1,12 @@
{
"name": "slack-github-action",
"version": "1.27.0",
"version": "1.27.1",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "slack-github-action",
"version": "1.27.0",
"version": "1.27.1",
"license": "MIT",
"dependencies": {
"@actions/core": "^1.11.1",
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "slack-github-action",
"version": "1.27.0",
"version": "1.27.1",
"description": "The official slack github action. Use this to send data into your Slack workspace",
"main": "dist/index.js",
"scripts": {