Bump the github-actions group across 1 directory with 2 updates

[dependabot]

Bumps the github-actions group with 2 updates in the / directory: actions/upload-artifact and slackapi/slack-github-action.

Updates actions/upload-artifact from 4.3.4 to 4.3.6

Release notes

Sourced from actions/upload-artifact's releases.

v4.3.6

What's Changed

• Revert to @​actions/artifact 2.1.8 by @​robherley in actions/upload-artifact#594

Full Changelog: actions/upload-artifact@v4...v4.3.6

v4.3.5

What's Changed

• Bump @​actions/artifact to v2.1.9 by @​robherley in actions/upload-artifact#588
  • Fixed artifact upload chunk timeout logic #1774
  • Use lazy stream to prevent issues with open file limits #1771

Full Changelog: actions/upload-artifact@v4.3.4...v4.3.5

Commits

• 834a144 Merge pull request #594 from actions/robherley/4.3.6
• 134dcf3 v4.3.6
• 73a0b9c revert back to @​actions/artifact 2.1.8
• 89ef406 Merge pull request #588 from actions/robherley/4.3.5
• 23d796d license updates
• e445c64 bump @​actions/artifact to v2.1.9
• See full diff in compare view

Updates slackapi/slack-github-action from 1.26.0 to 1.27.0

Release notes

Sourced from slackapi/slack-github-action's releases.

Slack Send V1.27.0

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/[email protected]
+   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.

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

... (truncated)

Commits

• 37ebaef Automatic compilation
• 5d1fb07 chore(release): tag version 1.27.0
• 3bc0671 chore(deps): bump axios to 1.7.5 (#332)
• b452451 feat: make the payload delimiter configurable for workflow webhook triggers (...
• c50e848 build(deps-dev): bump mocha from 10.5.2 to 10.7.0 (#328)
• e4a9c4b build(deps): bump @​slack/web-api from 7.2.0 to 7.3.2 (#327)
• 9a7f0fa build(deps-dev): bump chai from 4.4.1 to 4.5.0 (#326)
• 73b7062 build(deps-dev): bump eslint-plugin-jsdoc from 48.5.0 to 48.10.2 (#325)
• 3d5207b build(deps): bump https-proxy-agent from 7.0.4 to 7.0.5 (#320)
• 4e15b6a build(deps): bump @​slack/web-api from 7.0.4 to 7.2.0 (#323)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Trac Ticket Missing

This pull request is missing a link to a Trac ticket. For a contribution to be considered, there must be a corresponding ticket in Trac.

To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. More information about contributing to WordPress on GitHub can be found in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[dependabot]

Superseded by #7279.