Skip to content

chore(deps): update slackapi/slack-github-action action to v3#21

Open
smartway-bot[bot] wants to merge 1 commit intomasterfrom
renovate/slackapi-slack-github-action-3.x
Open

chore(deps): update slackapi/slack-github-action action to v3#21
smartway-bot[bot] wants to merge 1 commit intomasterfrom
renovate/slackapi-slack-github-action-3.x

Conversation

@smartway-bot
Copy link
Copy Markdown
Contributor

@smartway-bot smartway-bot bot commented Mar 23, 2026

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
slackapi/slack-github-action action major v1.18.0 -> v3.0.1

Release Notes

slackapi/slack-github-action (slackapi/slack-github-action)

v3.0.1: Slack GitHub Action v3.0.1

Compare Source

What's Changed

Alongside the breaking changes of @v3.0.0 and a new technique to run Slack CLI commands, we tried the wrong name to publish to the GitHub Marketplace 🐙 This action is now noted as The Slack GitHub Action in listings 🎶 ✨

🎨 Maintenance

Full Changelog: slackapi/slack-github-action@v3.0.0...v3.0.1

v3.0.0: Slack GitHub Action v3.0.0

Compare Source

The @v3.0.0 release had a hiccup on publish and we recommend using @​v3.0.1 or a more recent version when updating! Oops!

🎽 Running Slack CLI commands and the active Node runtime, both included in this release 👟 ✨

⚠️ Breaking change: Node.js 24 the runtime

This major version updates the GitHub Actions required runtime to Node.js 24. Most GitHub-hosted runners already include this, but self-hosted runners may need to be updated ahead of planned deprecations of Node 20 on GitHub Actions runners.

📺 Enhancement: Run Slack CLI commands

This release introduces a new technique for running Slack CLI commands directly in GitHub Actions workflows. Use this to install the latest version (or a specific one) of the CLI and execute commands like deploy for merges to main, manifest validate with tests, and other commands.

Gather a token using the following CLI command to store with repo secrets, then get started with an example below:

$ slack auth token
🧪 Validate an app manifest on pull requests

Check that your app manifest is valid before merging changes:

🔗 https://docs.slack.dev/tools/slack-github-action/sending-techniques/running-slack-cli-commands/validate-a-manifest

- name: Validate the manifest
  uses: slackapi/slack-github-action/cli@v3.0.0
  with:
    command: "manifest validate --app ${{ vars.SLACK_APP_ID }}"
    token: ${{ secrets.SLACK_SERVICE_TOKEN }}
🚀 Deploy your app on push to main

Automate deployments whenever changes land on your main branch:

🔗 https://docs.slack.dev/tools/slack-github-action/sending-techniques/running-slack-cli-commands/deploy-an-app

- name: Deploy the app
  uses: slackapi/slack-github-action/cli@v3.0.0
  with:
    command: "deploy --app ${{ vars.SLACK_APP_ID }} --force"
    token: ${{ secrets.SLACK_SERVICE_TOKEN }}

Any Slack CLI command can be passed through the command option without the "slack" prefix 🍀

The token input accepts a service token for authentication. You can gather this token by running slack auth token with the Slack CLI and storing the value as a repository secret.

The latest Slack CLI version is used by default, but a specific one can be set with the version input.

🏆 Huge thanks to @​ewanek1 for explorations and prototypes toward the scripted CLI technique!

For full documentation on the CLI technique, check out the docs and explore the related pages 📚

What's Changed
👾 Enhancements
📚 Documentation
🧰 Maintenance
🎁 Dependencies
👋 New Contributors

Full Changelog: slackapi/slack-github-action@v2.1.1...v3.0.0

v2.1.1: Slack Send v2.1.1

Compare Source

What's Changed

This release fixes an issue where substituted variables might've broken valid JSON or YAML parsings when using the payload-file-path input option.

🐛 Bug fixes
  • fix: parse provided payloads before replacing templated variables in #​449 - Thanks @​zimeg!
📚 Documentation
🤖 Dependencies
🧰 Maintenance

Full Changelog: slackapi/slack-github-action@v2.1.0...v2.1.1

v2.1.0: Slack Send v2.1.0

Compare Source

What's changed

This release improves error messages from odd payload parsings. An api option is now also available in inputs to change the destination of data with the method technique.

Read more on the new site for documentation: https://tools.slack.dev/slack-github-action/

👾 Enhancements
  • feat: include an 'api' option to customize the slack api method url in #​409 - Thanks @​zimeg!
🐛 Bug fixes
  • fix: avoid erroring if conflicting techniques are set from environment variables in #​374 - Thanks @​zimeg!
  • fix: require a custom 'api' url to send to instead of absolute urls as a 'method' in #​420 - Thanks @​zimeg!
  • fix: include cause of parsing errors in action output logs in #​431 - Thanks @​zimeg!
📚 Documentation
🤖 Dependencies
🧰 Maintenance
💌 New Contributors

Full Changelog: slackapi/slack-github-action@v2.0.0...v2.1.0

v2.0.0: Slack Send v2.0.0

Compare Source

YAML! And more API methods! With improved erroring! And more!

Sending data to Slack can now be done with the YAML format, and that data can be sent to [a Slack API method][methods] or technique of choice with the provided payload. And additional configurations can improve error handling or customize values between steps.

Breaking changes happen with this update and recommended migration strategies are detailed below. Adding this step to new workflows might prefer to follow the README instead 📚

What's changed

Both inputs of payload variables, techniques for sending the payload, additional configurations, and expected outputs were changed:

The following sections detail these changes with recommended changes for existing GitHub workflows using this step and certain features.

If something seems off after making these changes, please feel free to [open an issue][issues] for discussion! 👾

Sending variables

The source of variables remains the same, using one of the following inputs:

  • payload: Inputs written inline in your GitHub workflow file.
  • payload-file-path: Inputs gathered from a file.
  • No input: Uses the default event [context][event-context] with a [payload][event-payload] matching the GitHub event.
⚠️ Breaking changes
Only one payload input can be provided

This Action now exits with an error if both payload and payload-file-path are provided.

Prior to updating: Both options could be provided with payload being preferred.

Recommended change: Use either payload, payload-file-path, or neither, when providing inputs. But don't include both.

Only one technique to send can be provided

This Action now exits with an error if both method and webhook techniques are provided.

Prior to updating: Both techniques could be used to send the same payload.

Recommended change: Use either method or webhook to send data, but not both.

Variable replacements no longer happen by default

This Action now sends payload provided in a payload-file-path file exactly as is.

Prior to updating: Templatized variables in input files were replaced with the matching github or env variable:

{
  "channel": "${{ env.SLACK_CHANNEL_ID }}",
  "text": "A commit was made: ${{ github.sha }}"
}

Changing the above file into something like this before being sent:

{
  "channel": "C0123456789",
  "text": "A commit was made: 3982e204d2ae590e908dd1e279e63933da566c8c"
}

Recommended change: To continue replacing templated variables provided from the step env or default GitHub event [context][event-context] and [payload][event-payload], set the payload-templated variable to true.

Payload file path parsed option was removed

This Action removed the payload-file-path-parsed input option.

Prior to updating: This option, which defaulted to true, could be set to false to avoid replacing templatized variables in a provided payload-file-path file.

Recommended change: Remove this option if it's set to false or set the new payload-templated option to true to continue parsing the provided payload.

🎁 Enhancements
Payloads can now be written in YAML

This Action now supports writing payload or payload-file-path values with YAML!

Prior to updating: Values provided as payloads had to be JSON.

Recommended change: Optional. Format the input payload value as YAML to match the surrounding steps:

- name: Post to a Slack channel
  uses: slackapi/slack-github-action@v2.0.0
  with:
    method: chat.postMessage
    token: ${{ secrets.SLACK_BOT_TOKEN }}
    payload: |
      channel: ${{ secrets.SLACK_CHANNEL_ID }}
      text: "Greetings <@&#8203;channel>!"
Payload can now be written in unwrapped JSON

This Action now supports writing payload with unwrapped JSON, where surrounding braces are removed.

Prior to updating: Values provided as payloads had to be JSON.

Recommended change: Optional. Remove the surrounding braces from an existing payload value:

- name: Post to a Slack channel
  uses: slackapi/slack-github-action@v2.0.0
  with:
    method: chat.postMessage
    token: ${{ secrets.SLACK_BOT_TOKEN }}
    payload: |
      "channel": "${{ secrets.SLACK_CHANNEL_ID }}",
      "text": "Greetings <@&#8203;channel>!",
Sending techniques

The techniques for sending variables remains the same, using one of the following:

  • Technique 1: [Slack Workflow Builder][wfb]
  • Technique 2: [Slack API method][methods]
  • Technique 3: [Slack incoming webhook][incoming-webhook]

Changes for different technique might be different and are included in each of the following sections.

Technique 1: Slack Workflow Builder
⚠️ Breaking changes
The webhook type must be specified in webhook inputs

This Action now requires setting the webhook-type as a step input value.

Prior to updating: The webhook type could be omitted to send to Workflow Builder.

Recommended change: Set the webhook-type value to webhook-trigger, as shown in the example below.

Payload flattening no longer happens by default

This Action no longer flattens or stringifies payloads being sent to Workflow Builder by default.

Prior to updating: Payloads sent using a webhook trigger were flattened with a . delimiter and have values stringified before being sent.

Recommended change: If payload flattening is needed, use the payload-delimiter option. Inputs of Slack workflows should use an underscore _ as a delimiter to match expected inputs of Workflow Builder:

- name: Send GitHub Action data to a Slack workflow
  uses: slackapi/slack-github-action@v2.0.0
  with:
    payload-delimiter: "_"
    webhook: ${{ secrets.SLACK_WEBHOOK_URL }}
    webhook-type: webhook-trigger
🎁 Enhancements
The webhook URL can be specified in webhook inputs

This Action can now set the webhook URL as a step input.

Prior to updating: The SLACK_WEBHOOK_URL environment variable set this value.

Recommended change: Optional. Use the webhook input value, as shown above, to set the webhook URL.

Technique 2: Slack API methods

This technique can now send to [the Slack API methods][methods] and supports all [token][tokens] types!

⚠️ Breaking changes
The Slack API method now must be specified in inputs

This Action now requires that [the Slack API method][methods] is specified in inputs.

Prior to updating: Messages would be posted using chat.postMessage or chat.update behind the scenes.

Recommend change: Use the method that matches the message being posted, or use a different method:

- name: Post to a Slack channel
  uses: slackapi/slack-github-action@v2.0.0
  with:
    method: chat.postMessage
    token: ${{ secrets.SLACK_BOT_TOKEN }}
    payload: |
      channel: ${{ secrets.SLACK_CHANNEL_ID }}
      text: "Greetings <@&#8203;channel>!"

Note: Steps with update-ts should use chat.update as the method.

A token must be provided with other inputs

This Action expects a [token][tokens] as a step input value.

Prior to updating: Bot tokens were provided with the SLACK_BOT_TOKEN environment variable.

Recommended change: Provide the token scoped for the method as a step input, as shown above. The SLACK_TOKEN environment variable can also be used.

Inputs to the Slack API method must be provided in payloads

This Action now passes all provided values for payloads to the Slack API method.

Prior to updating: The channel-id and slack-message values were used.

Recommended change: Include the values sent to the Slack API method in the provided payload, as shown above.

Messages cannot be sent to multiple channels in one step

This Action can no longer send messages to multiple channels.

Prior to updating: Multiple channels could be provided to channel-id.

Recommended change: Update your GitHub workflow to repeat the same chat.postMessage step multiple times with different channel IDs.

Technique 3: Slack incoming webhook
⚠️ Breaking changes
The webhook type must be specified for incoming webhooks

This Action now requires setting the webhook-type as a step input value.

Prior to updating: The webhook type could be omitted to send to Workflow Builder.

Recommended change: Set the webhook-type value to incoming-webhook, as shown in the example below:

- name: Post a message in a channel
  uses: slackapi/slack-github-action@v2.0.0
  with:
    webhook: ${{ secrets.SLACK_WEBHOOK_URL }}
    webhook-type: incoming-webhook
    payload: |
      text: "Greetings from this step!"
🎁 Enhancements
The webhook URL must be specified for incoming webhooks

This Action can now set the webhook URL as a step input.

Prior to updating: The SLACK_WEBHOOK_URL environment variable set this value.

Recommended change: Optional. Use the webhook input value, as shown above, to set the webhook URL.

Additional configurations
🎁 Enhancements
Steps can exit with an error after a failed Slack API call

This Action can now exit if the Slack API returns an erroring response.

Prior to updating: Errors due to invalid payloads were ignored.

Recommended change: If a failing response from the Slack API should cause a step to fail, the errors value should be set to true since it defaults to false:

- name: Attempt to inverse a message
  uses: slackapi/slack-github-action@v2.0.0
  with:
    errors: true
    method: chat.reverse
    token: ${{ secrets.SLACK_BOT_TOKEN }}
    payload: |
      "message": "palindrome"
Failed requests can be retried various amounts of times

This Action can now retry requests that failed due to [rate limits][rate-limits].

Prior to updating: Rate limited requests were retried a fixed amount of times.

Recommended change: Set the retries option to a setting of choice:

- name: Attempt to inverse a message
  uses: slackapi/slack-github-action@v2.0.0
  with:
    method: chat.postMessage
    retries: rapid
    token: ${{ secrets.SLACK_BOT_TOKEN }}
    payload: |
      "message": "Good luck!"
Provided payloads can be flattened with a delimiter

This Action can now flatten and stringify payloads from any source.

Prior to updating: Payloads from the payload-file-path source were flattened with a period . delimiter by default.

Recommended change: Set the payload-delimiter option to an underscore _ to flatten and stringify nested payloads:

- name: Send GitHub Action data to a Slack workflow
  uses: slackapi/slack-github-action@v2.0.0
  with:
    payload-delimiter: "_"
    webhook: ${{ secrets.SLACK_WEBHOOK_URL }}
    webhook-type: webhook-trigger

In the example above, data from the default GitHub event [context][event-context] and event [payload][event-payload] are flattened before being sent with a webhook to Workflow Builder, matching the expected input shape of Workflow Builder.

Provided payloads can have templated variables replaced

This Action can now replace templated variables from any source.

Prior to updating: Templated variables were replaced by default in payloads from the payload-file-path source.

Recommended change: Set the payload-templated option to true to replace templated variables in provided payloads:

- name: Send custom JSON data to Slack workflow
  uses: slackapi/slack-github-action@v2.0.0
  with:
    payload-file-path: "./payload-slack-content.json"
    payload-templated: true
    webho

</details>

---

### Configuration

📅 **Schedule**: Branch creation - Between 12:00 AM and 06:59 AM, only on Monday ( * 0-6 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi40Mi4zIiwidXBkYXRlZEluVmVyIjoiNDIuNDIuMyIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 23, 2026

🛡️ The security scan result : Repo and Config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants