chore(deps): bump @slack/bolt from 3.22.0 to 4.1.0

[dependabot]

Bumps @slack/bolt from 3.22.0 to 4.1.0.

Release notes

Sourced from @​slack/bolt's releases.

@​slack/bolt@​4.1.0

What's Changed

• fix: Include metadata with Assistant say util by @​misscoded in slackapi/bolt-js#2300
• docs: concept focused nav by @​lukegalbraithrussell in slackapi/bolt-js#2302
• feat: Add title to setSuggestedPrompts utility by @​misscoded in slackapi/bolt-js#2308

Full Changelog: https://github.com/slackapi/bolt-js/compare/@​slack/bolt@​4.0.1...@​slack/bolt@​4.1.0

@​slack/bolt@​4.0.1

What's Changed

• Fix a bug where parsing assistant thread message event fails for beta feature enabled apps by @​seratch in slackapi/bolt-js#2298

Full Changelog: https://github.com/slackapi/bolt-js/compare/@​slack/bolt@​4.0.0...@​slack/bolt@​4.0.1

@​slack/bolt@​4.0.0

Bolt v4

What's Changed

New Features

Support for Agents & Assistants is now available!

Bolt now offers a simple and intuitive way to create an Agent/Assistant using the new Assistant class. Simply include the required callbacks and add the assistant to your App instance. Get up and running even quicker with a working, out-of-the-box example that utilizes OpenAI here.

Breaking Changes

We have prepared a migration guide to help BoltJS consumers migrate their Bolt v3 apps to v4.

While a few breaking changes were introduced, we don't expect a majority of bolt v3 users to require changing their apps to upgrade to v4. More complex apps may need a few tweaks. TL;DR is: if your bolt v3 app is built with TypeScript, or uses the ExpressReceiver or the AwsLambdaReceiver, or your app used previously-deprecated types or functions, best to read the migration guide.

Middleware Type Changes

In bolt we have a set of Slack*MiddlewareArgs types: for events, shortcuts, commands, and so on. They 'wrap' the underlying event payloads with additional middleware-relevant bits like a next() method, a context object for devs to augment, and so on.

Many of these types, for example the SlackEventMiddlewareArgs type, previously used a conditional to sometimes define particular additional helper utilities on the middleware arguments. For example, the say utility, or tacking on a convenience message property for message-event-related payloads. This was problematic in practice in TypeScript situations, not just internally (this change fixes slackapi/bolt-js#2135) within the bolt codebase but for developers as well: when the payload was not of a type that required the extra utility, these properties would be required to exist on the middleware arguments but have a value of undefined. Those of us trying to build generic middleware utilities would have to deal with TS compilation errors and needing to liberally type-cast to avoid these conditional mismatches with undefined.

Instead, these MiddlewareArgs types now conditionally create a type intersection when appropriate in order to provide this conditional-utility-extension mechanism. In practice that looks something like:

type SomeMiddlewareArgs<EventType extends string = string> = {
  // some type in here
} & (EventType extends 'message'
  // If this is a message event, add a `message` property
  ? { message: EventFromType<EventType> }
  : unknown
)

... (truncated)

Commits

• 9bcc680 Publish @slack/[email protected] (#2314)
• a17ec04 chore(deps): bump @​mdx-js/react from 3.0.1 to 3.1.0 in /docs (#2313)
• a839aaf chore(deps-dev): bump stylelint from 16.9.0 to 16.10.0 in /docs (#2312)
• 9addeda Docs: salesforce compliance adjustment (#2311)
• 78e0628 docs: general page cleanup (#2310)
• 4b6b25f Add title to setSuggestedPrompts utility (#2308)
• d3fe549 docs: concept focused nav (#2302)
• e51960b chore: remove old inapplicable gemfile from docs (#2305)
• 0aa69ad chore(deps-dev): bump @​types/node from 22.7.7 to 22.8.1 (#2306)
• 94c3e71 chore(deps): bump http-proxy-middleware from 2.0.6 to 2.0.7 in /docs (#2304)
• 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 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)

[github-actions]

Terraform Plan Changes

Terraform Plan: 0 to be created, 0 to be deleted, 1 to be updated, 0 to be replaced, 7 unchanged.

Resources to update

! azurerm_linux_web_app.gratibot_app_service