fix(deps): update module github.com/slack-go/slack to v0.17.3 #332
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
2435a93 to
e8fa0f9
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
e8fa0f9 to
8e30c27
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
8e30c27 to
4b735aa
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
4b735aa to
e289ecf
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
e289ecf to
5956d56
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
5956d56 to
5a7bfb2
Compare
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
6 times, most recently
from
5f18714 to
9162fa9
Compare
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
9162fa9 to
da26c8b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
da26c8b to
d16e3b8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
d16e3b8 to
c716d15
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
c716d15 to
c19c4ba
Compare
renovate
bot
changed the title
renovate
bot
changed the title
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
46d181f to
ad64fcd
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
ad64fcd to
b81bc0e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
b81bc0e to
476098d
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
231d934 to
476098d
Compare
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to 476098d in 1 minute and 22 seconds. Click for details.
- Reviewed
171lines of code in2files - Skipped
0files when reviewing. - Skipped posting
4draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. go.mod:16
- Draft comment:
Dependency update: github.com/slack-go/slack has been bumped to v0.17.3. This version introduces breaking changes (for example, modifications to MessageEvent and related types). Please verify that your code uses only the supported APIs and isn’t relying on any deprecated or manually constructed fields. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% The rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." This is a clear case of a dependency version change comment. While the comment might be technically correct about breaking changes, it's not something we should comment on according to the rules. The comment could be valuable since it warns about breaking changes that might affect the codebase. Maybe this is an exception to the dependency rule? No, the rules are very clear about not commenting on dependencies. The PR author should be responsible for testing their dependency updates, and any breaking changes would be caught during build/test. Delete this comment as it violates the explicit rule against commenting on dependency changes.
2. go.mod:19
- Draft comment:
The github.com/stretchr/testify dependency has been updated to v1.10.0. Review any test assertions to ensure compatibility with changes in this version. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is about a dependency update and suggests reviewing test assertions for compatibility. It doesn't provide a specific suggestion or point out a specific issue with the code. It falls under the rule of not commenting on dependency changes unless it's a recognized issue or specific suggestion.
3. go.mod:35
- Draft comment:
The github.com/gorilla/websocket dependency has been updated to v1.5.3. Confirm that any WebSocket integrations behave as expected with this newer release. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is asking the PR author to confirm that WebSocket integrations behave as expected with the updated dependency. This falls under the rule of not asking the author to ensure behavior is intended or tested, which is not allowed.
4. go.mod:5
- Draft comment:
A toolchain has been specified (go1.24.4) and the Go version is now set to 1.22. Ensure that the development and CI environments are updated accordingly to support these versions. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is asking the PR author to ensure that the development and CI environments are updated, which is against the rules. It does not provide a specific code suggestion or point out a specific issue with the code itself. Therefore, it should be removed.
Workflow ID: wflow_ssJu2XGLgrHq9Vk7
You can customize 
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
476098d to
f2e876f
Compare
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
f2e876f to
a27c772
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
3eff403 to
a27c772
Compare
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to a27c772 in 1 minute and 12 seconds. Click for details.
- Reviewed
171lines of code in2files - Skipped
0files when reviewing. - Skipped posting
4draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. go.mod:3
- Draft comment:
The Go version has been updated from 1.19 to 1.22, and a new 'toolchain go1.24.6' directive has been added. Please ensure that this upgrade is intentional and that your local and CI build environments support Go 1.22 (and ideally use the 1.24.6 toolchain). This change might require users to update their Go installations. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is related to a dependency change, specifically the Go version update. The comment asks the PR author to ensure that the upgrade is intentional and that environments support the new version, which violates the rule against asking for confirmation or ensuring behavior is intended. The comment also suggests that users might need to update their Go installations, which is informative rather than actionable. Therefore, this comment should be removed.
2. go.mod:16
- Draft comment:
The dependency 'github.com/slack-go/slack' has been updated from v0.11.3 to v0.17.3. This is a major jump and could introduce API changes (for example, in how SlackResponse is handled). Ensure that our codebase is compatible with the updates and review the upstream release notes for any necessary modifications. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is about a dependency update and suggests ensuring compatibility and reviewing release notes. According to the rules, comments on dependency changes should be ignored, especially if they suggest verifying compatibility or reviewing release notes.
3. go.mod:19
- Draft comment:
The 'github.com/stretchr/testify' dependency has been bumped to v1.10.0 from v1.9.0. This appears to be a minor update; however, please verify that our tests run correctly with the new version. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
4. go.mod:35
- Draft comment:
The 'github.com/gorilla/websocket' dependency has been updated to v1.5.3 from v1.4.2. This is likely a safe update, but please ensure that there are no regressions in the parts of our code that use websockets. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
Workflow ID: wflow_xZmbRfBLmJfslC9M
You can customize
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
a27c772 to
a996150
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
734e116 to
a996150
Compare
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to a996150 in 1 minute and 32 seconds. Click for details.
- Reviewed
169lines of code in2files - Skipped
0files when reviewing. - Skipped posting
5draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. go.mod:3
- Draft comment:
The Go language version has been updated from 1.19 to 1.22. Ensure that your development, CI, and build environments support Go 1.22. This may require updating your toolchain on older systems. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is related to a dependency change, specifically the Go language version. The comment advises the PR author to ensure compatibility with the new version across various environments, which is not allowed according to the rules. The comment does not provide a specific code suggestion or ask for a specific test to be written, which would be acceptable.
2. go.mod:14
- Draft comment:
The slack-go/slack dependency has been updated from v0.11.3 to v0.17.3. Given the significant evolution of this library (see its changelog), please double-check any code interfacing with Slack APIs for potential breaking changes. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is about a dependency change, specifically the slack-go/slack library. It asks the PR author to double-check for potential breaking changes due to the version update. This falls under the rule of not asking the author to double-check things, especially related to dependencies.
3. go.mod:17
- Draft comment:
The testify dependency was updated from v1.9.0 to v1.10.0. Although this is a minor version bump, verify that your tests (and any assertions based on its behavior) continue to operate as expected. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is about a dependency update, specifically a minor version bump of the 'testify' library. The comment suggests verifying that tests continue to operate as expected, which falls under asking the PR author to ensure behavior is intended or tested. This violates the rules against commenting on dependency changes and asking for verification of behavior.
4. go.mod:33
- Draft comment:
The gorilla/websocket dependency has been updated from v1.4.2 to v1.5.3. Make sure that any integration with this library still works as expected since some subtle changes in behavior or API improvements may be present. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is about a dependency update and suggests ensuring that the integration still works as expected. According to the rules, comments on dependency changes or asking the author to ensure behavior is intended are not allowed.
5. go.sum:175
- Draft comment:
The go.sum file has been updated with new checksums reflecting these dependency changes. It appears consistent with the version bumps in go.mod. Please confirm that no unexpected hashes were introduced. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is asking the PR author to confirm that no unexpected hashes were introduced, which violates the rule against asking for confirmation or verification. It also comments on dependency changes, which is not allowed.
Workflow ID: wflow_w496V7YKqLGITLs6
You can customize
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.11.3->v0.17.3Release Notes
slack-go/slack (github.com/slack-go/slack)
v0.17.3Compare Source
What's New
IsEmailConfirmedtoUserby @nlopes in #1458Fixes
In the previous version we introduced the ability to parse specific errors (more complex ones) but Slack can still send us a
string.stringis now the fallback type.Other
Also added a ./examples/README.md explaining the patterns that should be used.
Full Changelog: slack-go/slack@v0.17.2...v0.17.3
v0.17.2Compare Source
Features added
Timezoneparameter for the slackTimePickerBlockElementby @jamesjarvis in #1448 and #1449ImageBlockElementby @superturkey650 in #1444/migration.exchangeto the library by @nlopes in #1453/apps.connections.openhandler to slacktest by @prologic in #1447New Contributors
Full Changelog: slack-go/slack@v0.17.1...v0.17.2
v0.17.1Compare Source
This has the potential to be a breaking change if and only if you have been building
SlackResponseby 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 #1443 for more details.Features added
channel_unsharedevent by @nlopes in #1437This 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.
Detailed list of all of the changes
New Contributors
Full Changelog: slack-go/slack@v0.17.0...v0.17.1
v0.17.0Compare Source
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
Our
MessageEventhas 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 usesMessageEvent.FunctionExecutedEventhadInputsset asmap[string]stringbut that didn't allow enough flexibility - that has been changed tomap[string]interface.emojivalue in plain text blocks to be null by @calebmckay in #1354The
Emojifield inTextBlockObjectis now a pointer to ensure we can make a distinction betweennilandfalse. Only affects when unmarshalling.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.
PublishViewContext()now requires people to pass aPublishViewContextRequestwhich became a public type. If you callPublishViewContext()in your code, please adjust accordingly.AltTexttoAltTxtandSnippetTexttoSnippetType(inGetUploadURLExternalParametersandUploadFileV2Parameters) by @nlopes in #1422AppHomeOpenedEventViewis now a pointer by @nlopes in #1424This provides slightly better ergonomics in the case when there's no view yet.
Features added
MultiSelectBlockElementby @quantumsheep in #1373Headersfield to theFilestructure by @rntk in #1380RichTextValue(rich_text_value) toBlockActionby @borisputerka in #1385debugmode by @nlopes in #1393ForceInviteUsersToConversationby @nlopes in #1397Fixes
slacktestGetSeenOutboundMessagesrace condition by @askreet in #1362mrkdwnwhich the Slack API doesn't support by @nlopes in #1418Countfields as numbers by @nlopes in #1417omitemptyby @bassettb in #1412Detailed list of all of the changes
MultiSelectBlockElementby @quantumsheep in #1373emojivalue in plain text blocks to be null by @calebmckay in #1354ForceInviteUsersToConversationby @nlopes in #1397mrkdwnby @nlopes in #1418UploadToURL(fromuploadToURL) by @nlopes in #1422New Contributors
Full Changelog: slack-go/slack@v0.16.0...v0.17.0
v0.16.0Compare Source
👋 Hi folks,
I've tried my best to keep this version to just non-breaking changes but there are a couple of changes that might introduce breaking changes in rare circumstances.
If you're upgrading, please pay special attention to:
If you were using only what we provide in the library, this is a non-breaking change, but if not, it may be considered a breaking change.
Next release will likely bring a few required breaking changes (hard deprecations for example).
Thank you to everyone that contributed to this release 🥳
What's Changed
skin_tonefor rich text emoji element by @calebmckay in #1341New Contributors
Full Changelog: slack-go/slack@v0.15.0...v0.16.0
v0.15.0Compare Source
What's Changed
v0.15.0 is now available. It does contain minor breaking changes to two Block Kit elements along with a lot of new functionality.
Breaking Changes
Block Kit - Rich Text Section Date Element
If you are using the
RichTextSectionDateElementblock kit element, there is a new fieldFormatwhich is now required. It previously did not exist, but was marked as required in the Block Kit Documentation. Similarly, the functionNewRichTextSectionDateElementfunction signature has been updated to require the new parameter. While this may not have previously worked, the non-backwards compatible signature change prompts it to be identified as breaking change.Block Kit - Rich Text input Block Element
If you are using the
RichTextInputBlockElementblock kit element, theInitialValuefield type has been changed fromstringto*RichTextBlockto provide a more strongly typed experience. If you were previously passing a pre-formatted JSON object you will need to update your input to use theRichTextBlockstruct instead.Enhancements
calls.*apis andType: callin blockkit by @winston-stripe in #1190Bug Fixes
formatfield to rich text date blocks by @luke-josh in #1317Chores
New Contributors
Full Changelog: slack-go/slack@v0.14.0...v0.15.0
v0.14.0Compare Source
What's Changed
v0.14.0 is now available. It contains no breaking changes but does include several pieces of new functionality and long-standing bug fixes.
Enhancements
metadatawhen receiving aMessageEventover WebSocket by @rfratto in #1307Fileevent from a Slack Connect Channel by @zFlabmonsta in #1312slack_filein the image block by @rhysm in #1311AppRateLimitedevents in theParseEventfunction by @nemuvski in #1308conversations.infoWeb API method by @ku in #1228Bug Fixes
UpdateRemoteFileContextandUpdateRemoteFileand Image Previews would return aninvalid_autherror by @EkeMinusYou in #1117Chores / Code Cleanup
ioutilwithioandospackages by @nakamasato in #1310New Contributors
Full Changelog: slack-go/slack@v0.13.1...v0.14.0
v0.13.1Compare Source
What's Changed
v0.13.1 is now available. It contains no breaking changes but does expose some new fields previously unavailable.
Enhancements
UnfurlLinksandUnfurlMediatoWebhookMessageby @lheiskan in #1208isReadOnlyproperty toConversationstruct by @GGonryun in #1232Bug Fixes
UploadFileV2when using text content by @calebmckay in #1291Channeloptional onUploadFileV2by @0xdeafcafe in #1293Chores / Code Cleanup
files.uploadby @lorenzoaiello in #1300Documentation Updates
Paginationby @adamrothman in #1201ConversationHistoryby @lorenzoaiello in #1302AddRemoteFileandDeleteFileby @lorenzoaiello in #1303New Contributors
Full Changelog: slack-go/slack@v0.13.0...v0.13.1
v0.13.0Compare Source
What's Changed
Breaking changes
team_idparameter for use with org-wide app by @candiduslynx in #1283:Changed interface:
Client.GetBotInfo(bot string) (*Bot, error)Client.GetBotInfo(parameters GetBotInfoParameters) (*Bot, error)Client.GetBotInfoContext(ctx context.Context, bot string)Client.GetBotInfoContext(ctx context.Context, parameters GetBotInfoParameters)Client.GetTeamProfile() (*TeamProfile, error)GetTeamProfile(teamID ...string) (*TeamProfile, error)GetTeamProfileContext(ctx context.Context) (*TeamProfile, error)GetTeamProfileContext(ctx context.Context, teamID ...string) (*TeamProfile, error)Client.GetBillableInfo(user string) (map[string]BillingActive, error)Client.GetBillableInfo(params GetBillableInfoParams) (map[string]BillingActive, error)Client.GetBillableInfoContext(ctx context.Context, user string) (map[string]BillingActive, error)Client.GetBillableInfoContext(ctx context.Context, params GetBillableInfoParams) (map[string]BillingActive, error)Client.GetBillableInfoForTeam() (map[string]BillingActive, error)Client.GetBillableInfowith empty paramsClient.GetBillableInfoForTeamContext(ctx context.Context) (map[string]BillingActive, error)Client.GetBillableInfoContextwith empty paramsBug fixes
Enhancements
team_idparameter for use with org-wide app by @candiduslynx in #1283New Contributors
Full Changelog: slack-go/slack@v0.12.5...v0.13.0
v0.12.5Compare Source
What's Changed
BUGFIX - deal with "true", true, "false", false.
Full Changelog: slack-go/slack@v0.12.4...v0.12.5
v0.12.4: Non-breaking updates roll-upCompare Source
What's Changed
URLonNewButtonBlockElementvia.WithURL()by @joshbranham in #1250New Contributors
Full Changelog: slack-go/slack@v0.12.3...v0.12.4
v0.12.3Compare Source
What's Changed
Bug fixes
omitemptyto ConfirmationBlockObject.Deny by @kamil-gwozdz in #1224Security
Enhancements / Improvements
New Contributors
Full Changelog: slack-go/slack@v0.12.2...v0.12.3
v0.12.2Compare Source
What's Changed
Bug fixes
Enhancements / Improvements
Misc
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.