Update module github.com/slack-go/slack to v0.17.3 #214
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]](https://avatars.githubusercontent.com/in/2740?s=80&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
5a5f7f2 to
9569d02
Compare
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
9569d02 to
0176556
Compare
renovate
bot
changed the title
ℹ 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
0176556 to
dea307a
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
dea307a to
d5c5096
Compare
renovate
bot
force-pushed
the
renovate/github.com-slack-go-slack-0.x
branch
from
d5c5096 to
d0da24d
Compare
renovate
bot
changed the title
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.14.0->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
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 becomes conflicted, 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.