Repository navigation
chore: release - #2855
Merged
Merged
chore: release#2855
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
15 times, most recently
from
November 20, 2026 04:23
7c08d98 to
60d5f53
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 04:46
60d5f53 to
81d1e30
Compare
zimeg
marked this pull request as ready for review
November 20, 2026 05:11
Member
|
zimeg
approved these changes
Nov 20, 2026
zimeg
left a comment
Member
There was a problem hiding this comment.
🚀 Version bumps and changelogs match the merged changesets, CI is green on main, and the regenerated response types compile against 8.4.0 in both directions apart from expected widenings.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2855 +/- ##
==========================================
+ Coverage 94.44% 94.56% +0.11%
==========================================
Files 68 68
Lines 10942 10942
Branches 700 697 -3
==========================================
+ Hits 10334 10347 +13
+ Misses 579 568 -11
+ Partials 29 27 -2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@slack/[email protected]
Minor Changes
app link,app settings,app unlink,blocks preview,createtemplate categories,docs,env initandproject init.Patch Changes
3c473ca: fix: stop the output wait timeout from killing
runandactivity --tailplatform.runStartandplatform.activityTailStartpassed theirtimeoutto the spawned Slack CLI process as well as to the wait for output. Node then stopped the process once the timeout passed, even after the expected output arrived. The timeout now applies only to the wait for output, so these processes keep running until they are stopped.653fc5c: fix(cli-test): wait up to 60 seconds for commands to finish
Commands now wait up to 60 seconds for the Slack CLI to finish before timing out, up from 30 seconds. Some commands, such as
slack createwith a Bolt template on Windows, can take close to 30 seconds.@slack/[email protected]
Minor Changes
apps.icon.setmethodapps.managed.permissions.setmethodassistant.search.contextandassistant.search.infomethodsPatch Changes
enterpriseinassistant.search.contextcontent_typesand list its arguments in the reference order@slack/[email protected]
Minor Changes
c043b50: feat: warn when a URL pattern mismatches the webhook class
IncomingWebhookandWebhookTriggernow accept optionalloggerandlogLeveloptions. On construction,IncomingWebhookwarns when the URL contains/triggers/andWebhookTriggerwarns when the URL contains/services/, so a URL used with the wrong class shows up in the logs before anything is sent.Patch Changes
713f176: fix: use the
fetch,timeoutandretryConfiggiven toIncomingWebhook.send()send()accepted these options but only used the ones given to the constructor. Options given tosend()now apply to that call, and fall back to the constructor's when left out.8011e1d: fix: stop
IncomingWebhook.send()from posting thetimeoutandretryConfigoptionsThese options were already removed from the constructor defaults, but options given to
send()were merged in afterward and posted in the payload. They're now removed from every payload before it's sent.Updated dependencies [fd8f6dd]
Updated dependencies [bce2a92]
@slack/[email protected]
Patch Changes
bot_profilefield toThreadBroadcastMessageEvent.bot_idfield toThreadBroadcastMessageEvent.