Bump github.com/slack-go/slack from 0.15.0 to 0.17.1

[dependabot]

Bumps github.com/slack-go/slack from 0.15.0 to 0.17.1.

Release notes

Sourced from github.com/slack-go/slack's releases.

v0.17.1

This has the potential to be a breaking change if and only if you have been building SlackResponse by hand, which you shouldn't 😬. If you are, my apologies for adding this in a minor version, I thought the likelihood of this to be very very low. See slack-go/slack#1443 for more details.

Features added

• Add channel_unshared event by @​nlopes in slack-go/slack#1437
• Add missing Blocks to UploadFileContextV2 by @​dalyndalton in slack-go/slack#1435 This adds the missing optional dependency for Blocks to the upload file method, allowing users to use rich blocks and buttons during the file upload process.
• Return Errors field in SlackErrorResponse by @​nlopes in slack-go/slack#1443

Detailed list of all of the changes

• chore: add CI test status badge to README by @​nlopes in slack-go/slack#1431
• feat: add channel_unshared event by @​nlopes in slack-go/slack#1437
• chore: add test for section block expand option by @​nlopes in slack-go/slack#1440
• chore: order inner events vars alphabetically by @​nlopes in slack-go/slack#1442
• chore: better events example code by @​nlopes in slack-go/slack#1441
• feat: Add missing Blocks to UploadFileContextV2 by @​dalyndalton in slack-go/slack#1435
• feat: return Errors field in SlackErrorResponse by @​nlopes in slack-go/slack#1443
• doc: add README.md to examples/eventsapi by @​nlopes in slack-go/slack#1445

New Contributors

• @​dalyndalton made their first contribution in slack-go/slack#1435

Full Changelog: slack-go/slack@v0.17.0...v0.17.1

v0.17.0

MAJOR BREAKING CHANGES

This release has a few major breaking changes. And a couple require developers to pay a bit of attention, else their programs will break. I am sorry this is the case but such is life sometimes.

See below for the most important, and trickier breaking changes.

Breaking changes

• Fix message event struct by @​paprikati in slack-go/slack#1391 and slack-go/slack#1408 Our MessageEvent has been quite wrong for a while. This should fix it but it does mean folks will have to change their code to cope with this new structure. Please be extra vigilant in areas of your code that uses MessageEvent.
• Function execution events now correctly accept interfaces not strings by @​ProjectBarks in slack-go/slack#1357 FunctionExecutedEvent had Inputs set as map[string]string but that didn't allow enough flexibility - that has been changed to map[string]interface.
• Allow emoji value in plain text blocks to be null by @​calebmckay in slack-go/slack#1354 The Emoji field in TextBlockObject is now a pointer to ensure we can make a distinction between nil and false. Only affects when unmarshalling.
• Remove Legacy Workflows by @​lorenzoaiello in slack-go/slack#1350 Slack has deprecated legacy workflows for a long time, and beginning September 26, 2024, Slack stopped executing workflows containing a "step from app." See more at https://api.slack.com/changelog/2023-08-workflow-steps-from-apps-step-back.
• Implement PublishViewContext to keep hash optional by @​ishitamundhra in slack-go/slack#1322 PublishViewContext() now requires people to pass a PublishViewContextRequest which became a public type. If you call PublishViewContext() in your code, please adjust accordingly.
• Renamed AltText to AltTxt and SnippetText to SnippetType (in GetUploadURLExternalParameters and UploadFileV2Parameters) by @​nlopes in slack-go/slack#1422
• AppHomeOpenedEvent View is now a pointer by @​nlopes in slack-go/slack#1424 This provides slightly better ergonomics in the case when there's no view yet.

Features added

• Add markdown block by @​nlopes in slack-go/slack#1372
• Add filter in MultiSelectBlockElement by @​quantumsheep in slack-go/slack#1373

... (truncated)

Commits

• 965251a doc: add README.md to examples/eventsapi (#1445)
• 4620cce doc: add README.md to examples/eventsapi
• b42f029 feat: return Errors field in SlackErrorResponse (#1443)
• da97682 feat: return Errors field in SlackErrorResponse
• b4aa697 feat: Add missing Blocks to UploadFileContextV2 (#1435)
• fe840f9 chore: better events example code (#1441)
• cee6dd9 chore: order inner events vars alphabetically (#1442)
• 4e84670 chore: add test for section block expand option (#1440)
• 1905f7e chore: order inner events vars alphabetically
• f3370d0 chore: add test for section block expand option
• 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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[what-the-diff]

PR Summary

• Upgraded slack-go/slack library
  The version of the slack-go/slack library that our application depends upon has been updated from v0.15.0 to v0.17.1. This should enhance the interaction functionality of the app with Slack.
• Updated go.sum for slack-go/slack
  As a consequence of the previous point, the check-sum value recorded in go.sum for slack-go/slack has also been updated to match the new version v0.17.1.
• Updated go-test/deep library version
  The go-test/deep library, which helps us check equality between data types, has been updated from v1.0.4 to v1.1.1. As a result, our testing process should now be more effective and reliable.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)