chore(deps): bump slackapi/slack-github-action from 1 to 4

[dependabot]

Bumps slackapi/slack-github-action from 1 to 4.

Release notes

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

Slack GitHub Action v4.0.0

Major Changes

• b1974f0: build: parse yaml with more strict multiline indentation rules

  Internal dependencies of js-yaml@v5 make YAML parsing more strict and compliant with the YAML specification. Indentation is now required for values that span multiple lines against the base value.

  See the YAML line prefixes spec for the expected indentation rule:

   channel: "C0123"
  text: "first line
  second line"
  second line"

Patch Changes

• 654bb72: chore: provide global fetch proxied configurations with updates to web api and webhook packages

Slack GitHub Action v3.0.5

Patch Changes

• 96fddbe: fix: revert multiline yaml parsing indentation change

Slack GitHub Action v3.0.4

Patch Changes

• fa03fe4: refactor: send webhooks with the @slack/webhook package

Slack GitHub Action v3.0.3

Patch Changes

• 66834e4: feat: add instrumentation to address error rates

Slack GitHub Action v3.0.2

Patch Changes

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

Slack GitHub Action v3.0.1

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 🎶 ✨

... (truncated)

Changelog

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

slack-github-action

4.0.0

Major Changes

• b1974f0: build: parse yaml with more strict multiline indentation rules

  Internal dependencies of js-yaml@v5 make YAML parsing more strict and compliant with the YAML specification. Indentation is now required for values that span multiple lines against the base value.

  See the YAML line prefixes spec for the expected indentation rule:

   channel: "C0123"
  text: "first line
  second line"
  second line"

Patch Changes

• 654bb72: chore: provide global fetch proxied configurations with updates to web api and webhook packages

3.0.5

Patch Changes

• 96fddbe: fix: revert multiline yaml parsing indentation change

3.0.4

Patch Changes

• fa03fe4: refactor: send webhooks with the @slack/webhook package

3.0.3

Patch Changes

• 66834e4: feat: add instrumentation to address error rates

3.0.2

Patch Changes

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

Commits

• dcb1066 chore: release
• 53861e0 chore: release (#645)
• b1974f0 build!: parse yaml with more strict multiline indentation rules (#640)
• 947ed06 build(deps): bump undici from 7.28.0 to 8.7.0 (#653)
• 03922a9 chore: track undici-types to the resolved undici version (#652)
• 31d473e build(deps-dev): bump typescript from 6.0.3 to 7.0.2 (#651)
• 3ca6997 build(deps-dev): bump sinon and @​types/sinon (#649)
• 26a5ad3 build(deps): bump actions/setup-node from 6.4.0 to 7.0.0 (#647)
• 5092efb build(deps-dev): bump @​biomejs/biome from 2.5.3 to 2.5.4 (#650)
• 3548c3e build(deps): bump slackapi/slack-github-action from 3.0.3 to 3.0.5 (#646)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-21 08:35 UTC · Rule: dependabot-develop · triggered by merge protections
• ✅ Checks passed · in-place
• ✅ Merged — 2026-08-21 08:44 UTC · at ef5f22364cbf58109d013247481bc448d526dadd · squash

This pull request spent 8 minutes 33 seconds in the queue, including 49 seconds running CI.

Required conditions to merge

• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr-template
  • check-neutral = validate-pr-template
  • check-skipped = validate-pr-template

[github-actions]

⏱️ Aging and SLA annotation

• Age: 0 day(s)
• SLA state: Within SLA
• Thresholds: warn at 7 days, breach at 14 days
• Last updated: 2026-08-21T08:41:07.042Z

Maintained by project-meta-sync workflow.

[github-actions]

❌ Branch Name Validation Failed

The branch name dependabot/github_actions/slackapi/slack-github-action-4 does not follow the LightSpeed branching strategy.

Required Format

{type}/{scope}-{short-title}

• type: one of the allowed prefixes (lowercase)
• scope: lowercase, hyphens only (no underscores or uppercase)
• title: lowercase, hyphens only (no underscores or uppercase)

Allowed Branch Types

feat, fix, hotfix, release, refactor, chore, docs, test, perf, ci, build, deps, security, revert, research, design, a11y, ux, i18n, ops, proto, ds, api, schema, telemetry, content, seo, config, migrate, qa, uat, audit, codex

Valid Examples

• ✓ feat/branch-naming-enforcement
• ✓ fix/validation-script-bug
• ✓ chore/update-dependencies
• ✓ docs/branching-strategy-guide
• ✓ hotfix/critical-security-patch

Invalid Examples

• ✗ claude/my-branch (type "claude" not allowed)
• ✗ Feature/MyBranch (uppercase not allowed)
• ✗ fix-bug (missing type prefix)
• ✗ feat/my_feature (underscores not allowed)
• ✗ feat/MyFeature (uppercase not allowed)

Solution

Rename your branch to follow the pattern and update the PR.

For more information, see docs/BRANCHING_STRATEGY.md.