Skip to content

chore(deps): update slackapi/slack-github-action action to v1.27.1 (main)#4197

Closed
elastic-renovate-prod[bot] wants to merge 1 commit intomainfrom
renovate/main-slackapi-slack-github-action-1.x
Closed

chore(deps): update slackapi/slack-github-action action to v1.27.1 (main)#4197
elastic-renovate-prod[bot] wants to merge 1 commit intomainfrom
renovate/main-slackapi-slack-github-action-1.x

Conversation

@elastic-renovate-prod
Copy link
Copy Markdown
Contributor

@elastic-renovate-prod elastic-renovate-prod bot commented Apr 6, 2026

This PR contains the following updates:

Package Type Update Change
slackapi/slack-github-action action minor v1.24.0 -> v1.27.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v1.27.1: Slack Send V1.27.1

Compare Source

What's changed

This release tags multiple updates to dependencies and a clarification in documentation 📚

No changes are needed to update from slackapi/slack-github-action@v1.27.0 - other than bumping the version - but ongoing development is now happening on version @v2 and @v1 is no longer planning to receive significant updates after this.

Please stay tuned for upcoming changes, and may all of your workflows run well ❤️

📚 Documentation
🧪 Maintenance
📦 Dependencies

Full Changelog: slackapi/slack-github-action@v1.27.0...v1.27.1

v1.27.0: Slack Send V1.27.0

Compare Source

What's changed

This release introduces an optional payload-delimiter parameter for flattening nested objects with a customized delimiter before the payload is sent to Slack Workflow Builder when using workflow webhook triggers.

  - name: Send a custom flattened payload
    uses: slackapi/slack-github-action@v1.27.0
+   with:
+     payload-delimiter: "_"
    env:
      SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

Setting this value to an underscore (_) is recommended when using nested inputs within Workflow Builder to match expected input formats of Workflow Builder, but the actual value can be changed to something else! This "flattening" behavior did exist prior to this version, but used a period (.) which is not valid for webook inputs in Workflow Builder.

Flattening example

The resulting output of flattened objects is not always clear, but the following can hopefully serve as a quick reference as well as these specs when using _ as the delimiter:

Input:

{
    "apples": "tree",
    "bananas": {
        "truthiness": true
    }
}

Output:

{
    "apples": "tree",
    "bananas_truthiness": "true"
}

Notice that bananas_truthiness is also stringified in this process, as part of updating values to match the expected inputs of Workflow Builder!

Changes

In addition to the changes above, the following lists all of the changes since the prior version with the complete changelog changes found here: slackapi/slack-github-action@v1.26.0...v1.27.0

🎁 Enhancements
📚 Documentation
🔒 Security
🧪 Maintenance
📦 Dependencies

🎉 New contributors

v1.26.0: Slack Send V1.26.0

Compare Source

What's Changed

This release provides an escape hatch for sending the JSON content of a payload file exactly as is, without replacing any templated variables!

Previously a payload file was parsed and templated variables were replaced with values from github.context and github.env. Any undefined variables were replaced with ??? in this process, which might have caused questions.

That remains the default behavior, but now the JSON contents of a payload file can be sent exactly as written by setting the payload-file-path-parsed input to false:

- name: Send custom JSON data to Slack workflow
  id: slack
  uses: slackapi/slack-github-action@v1.26.0
  with:
    payload-file-path: "./payload-slack-content.json"
    payload-file-path-parsed: false
  env:
    SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

With this change, the contents of the example payload-slack-content.json will be sent to a webhook URL exactly as is!

Recent commits

Enhancements
Documentation
Maintenance
Dependencies

New Contributors

Full Changelog: slackapi/slack-github-action@v1.25.0...v1.26.0

v1.25.0: Slack Send V1.25.0

Compare Source

What's Changed

New Contributors

Full Changelog: slackapi/slack-github-action@v1.24.0...v1.25.0


Configuration

📅 Schedule: Branch creation - "* 1 * * 1-5" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 has been generated by Renovate Bot.

@elastic-renovate-prod elastic-renovate-prod bot requested a review from a team as a code owner April 6, 2026 22:45
@elastic-renovate-prod elastic-renovate-prod bot added dependencies Pull requests that update a dependency file Team:Cloud-Security-Posture renovate labels Apr 6, 2026
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-slackapi-slack-github-action-1.x branch from 91abf02 to 3c26712 Compare April 6, 2026 23:15
@elastic-renovate-prod elastic-renovate-prod bot enabled auto-merge (squash) April 8, 2026 20:13
@olegsu olegsu closed this Apr 9, 2026
auto-merge was automatically disabled April 9, 2026 12:23

Pull request was closed

@elastic-renovate-prod
Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.27.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@elastic-renovate-prod elastic-renovate-prod bot deleted the renovate/main-slackapi-slack-github-action-1.x branch April 9, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant