Skip to content

Update slackapi/slack-github-action action to v3#40

Merged
garrmark merged 1 commit into
mainfrom
renovate/slackapi-slack-github-action-3.x
May 5, 2026
Merged

Update slackapi/slack-github-action action to v3#40
garrmark merged 1 commit into
mainfrom
renovate/slackapi-slack-github-action-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 13, 2026 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
slackapi/slack-github-action action major v2.1.1 → v3.0.3

Release Notes

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

v3.0.3

Compare Source

v3.0.2: Slack GitHub Action v3.0.2

Compare Source

Patch Changes
  • 79529d7: fix: resolve url.parse deprecation warning for webhook techniques

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

Compare Source

v3.0

Compare Source

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/slackapi-slack-github-action-3.x branch from 285ed95 to 81be03d Compare March 26, 2026 18:10
@renovate renovate Bot force-pushed the renovate/slackapi-slack-github-action-3.x branch 2 times, most recently from 2dde4fe to efc428b Compare April 21, 2026 18:55
@renovate renovate Bot force-pushed the renovate/slackapi-slack-github-action-3.x branch from efc428b to 1383eb6 Compare April 23, 2026 10:14
@renovate renovate Bot force-pushed the renovate/slackapi-slack-github-action-3.x branch from 1383eb6 to f554159 Compare May 2, 2026 01:57
@garrmark garrmark requested a review from Copilot May 5, 2026 18:09
Copilot AI reviewed May 5, 2026
View reviewed changes
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Slack notification steps in the release workflows to use slackapi/slack-github-action v3 (pinned by commit SHA), keeping the existing chat.postMessage technique and inputs.

Changes:

  • Bump slackapi/slack-github-action from v2.1.1 to v3.0.3 in the PyPI publish workflow.
  • Bump slackapi/slack-github-action from v2.1.1 to v3.0.3 in the version bump/release workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/publish-to-pypi.yml Updates the Slack notification action reference to v3.0.3 (pinned SHA).
.github/workflows/bump-version.yml Updates the Slack notification action reference to v3.0.3 (pinned SHA).

@garrmark garrmark merged commit 731e558 into main May 5, 2026
5 checks passed
@renovate renovate Bot deleted the renovate/slackapi-slack-github-action-3.x branch May 5, 2026 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@garrmark