Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 19, 2024

This PR contains the following updates:

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

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
  • docs(fix): reference octokit context and github event webhook payloads in variables in #​348 - thanks @​zimeg!
🧪 Maintenance
  • ci: include the slack health score as part of ci tests in #​346 - thanks @​zimeg!
📦 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
  • ci(test): collect environment secrets from a prepared staging environment by @​zimeg in #​294
  • ci(test): share environment secrets with pull requests from forked prs by @​zimeg in #​297
Dependencies

New Contributors

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


Configuration

📅 Schedule: 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-1.x branch from faa2eac to 7c47699 Compare August 28, 2024 23:34
@renovate renovate bot changed the title chore(deps): update slackapi/slack-github-action action to v1.26.0 chore(deps): update slackapi/slack-github-action action to v1.27.0 Aug 28, 2024
@renovate renovate bot force-pushed the renovate/slackapi-slack-github-action-1.x branch from 7c47699 to aca9d7a Compare November 14, 2024 21:52
@renovate renovate bot changed the title chore(deps): update slackapi/slack-github-action action to v1.27.0 chore(deps): update slackapi/slack-github-action action to v1.27.1 Nov 14, 2024
@renovate renovate bot force-pushed the renovate/slackapi-slack-github-action-1.x branch from aca9d7a to 21662f1 Compare December 2, 2024 10:03
@renovate renovate bot force-pushed the renovate/slackapi-slack-github-action-1.x branch from 21662f1 to 4aae9cb Compare April 10, 2025 09:35
@renovate renovate bot force-pushed the renovate/slackapi-slack-github-action-1.x branch from 4aae9cb to 702f2b9 Compare July 28, 2025 13:15
@renovate renovate bot force-pushed the renovate/slackapi-slack-github-action-1.x branch from 702f2b9 to 4156357 Compare August 10, 2025 14:08
@renovate renovate bot force-pushed the renovate/slackapi-slack-github-action-1.x branch from 4156357 to 76337cd Compare September 25, 2025 18:45
@renovate renovate bot force-pushed the renovate/slackapi-slack-github-action-1.x branch from 76337cd to f52a4a9 Compare October 9, 2025 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants