⬆️ bump the go-dependencies group with 3 updates - #600

Sourced from github.com/chromedp/cdproto's changelog.

v0.159.1 - 2026-11-03

• Chromium: 159.0.8140.1 (was 159.0.8134.1)
• V8: 15.9.67 (was 15.9.58)
• API changes since v0.159.0: 3 incompatible, 5 compatible

By package, as removed, changed and added names:

browser 1 removed 0 changed 0 added page 2 removed 0 changed 0 added webmcp 0 removed 0 changed 5 added

v0.159.0 - 2026-10-31

• Chromium: 159.0.8134.1 (was 158.0.8127.1)
• V8: 15.9.58 (was 15.8.62)
• API changes since v0.158.6: 0 incompatible, 4 compatible

By package, as removed, changed and added names:

page 0 removed 0 changed 4 added

v0.158.6 - 2026-10-27

• Chromium: 158.0.8127.1 (was 158.0.8124.1)
• V8: 15.8.62 (was 15.8.47)
• API changes since v0.158.5: 0 incompatible, 1 compatible

By package, as removed, changed and added names:

preload 0 removed 0 changed 1 added

v0.158.5 - 2026-10-25

• Chromium: 158.0.8124.1 (was 158.0.8115.1)
• V8: 15.8.47 (was 15.8.24)
• API changes since v0.158.4: 0 incompatible, 1 compatible

By package, as removed, changed and added names:

network 0 removed 0 changed 1 added

v0.158.4 - 2026-10-21

• Chromium: 158.0.8115.1 (was 158.0.8111.1)
• V8: 15.8.24 (was 15.8.18)
• API changes since v0.158.3: 0 incompatible, 2 compatible

By package, as removed, changed and added names:

... (truncated)

• 6239158 Updating to 159.0.8140.1_15.9.67 definitions
• 972fb83 Updating to 159.0.8134.1_15.9.58 definitions
• 448f657 Updating to 158.0.8127.1_15.8.62 definitions
• ffa9e35 Updating to 158.0.8124.1_15.8.47 definitions
• 3760c3c Updating to 158.0.8115.1_15.8.24 definitions
• 9e2f767 Updating to 158.0.8111.1_15.8.18 definitions
• ca3270c Updating to 158.0.8110.1_15.8.17 definitions
• baa75cb Updating to 158.0.8108.1_15.8.17 definitions
• 2c43b54 Updating to 158.0.8104.1_15.7.112 definitions
• a4494e9 Updating to 157.0.8103.0_15.7.112 definitions
• Additional commits viewable in compare view

Sourced from github.com/chromedp/chromedp's releases.

v0.22.0

New: Listen and ListenBrowser call a func for each event of the tab or the browser, in the order in which the events arrive from Chrome. The target calls the func before it reads the next message, so the func sees an event that arrived before the reply to a command before that command returns. Events and BrowserEvents give one iterator for each event type and give neither guarantee, so they stay the recommended API, and Listen is the lower level tool for code that needs the order across event types. The func gets the typed events of cdproto and no replies to commands. It runs in the loop that reads the messages of the tab, so it must return fast, must not run a command, must not call Listen and must not panic. See docs/API.md, example 28, and the decision docs/decisions/2026-11-04-export-the-ordered-event-listener.md. The idea comes from discussion #1645 by onsi.

v0.21.1

Fix a panic, close of closed channel, in the handling of DOM.documentUpdated. When DOM.getDocument failed, for example because the tab was closing, the frame kept its old root node, and the next DOM.documentUpdated event closed the channel of that root again. The frame now clears the root first. Thanks to Dhruv Jain (#1644). The module also requires cdproto v0.159.0 now.

• da4225f Export the ordered event listener as Listen and ListenBrowser
• d42b1ae Update cdproto to v0.159.0
• cff4a57 Update the README for the distrust example
• 1edebf2 Clear the root node after documentUpdated invalidates it
• See full diff in compare view

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

v0.34.0

Huge thank you to Michal Mazurek (@​akfaew) for submitting a bunch of patches for this release.

Breaking changes — read before upgrading

[!WARNING] v0.34.0 includes breaking API, decoding, serialization, and event-dispatch changes.

Your code may fail to compile. Code that still compiles may decode, serialize, or route events differently. Malformed payloads can cause an entire Events API event to be rejected.

Review every item below before upgrading, including interfaces, mocks, custom event decoders, and stored payloads.

1. Retired user APIs have been removed

• SetUserAsActive and SetUserAsActiveContext are gone. Remove these calls. SetUserPresence still supports away and auto, but marking user as active is gone.
• GetUsersOptionPresence is gone. Remove it from GetUsers, GetUsersContext, and GetUsersPaginated calls. User-list requests no longer send the retired presence parameter. Use GetUserPresence or GetUserPresenceContext for individual presence checks.

2. Team-info method signatures have changed

GetTeamInfo, GetTeamInfoContext, GetOtherTeamInfo, and GetOtherTeamInfoContext now accept ...GetTeamInfoOption. Update interfaces, mocks, and assigned function types to include the variadic parameter. Existing direct calls remain valid.

3. Auth-provider blocks have a new concrete type and lose raw JSON

[!NOTE] This is a brand new block. For now experimental as it doesn't yet appear in the slack docs but is already part of their official node sdk.

• auth_provider blocks now decode as *AuthProviderBlock, replacing *UnknownBlock. Update type assertions and type switches.

An unchanged JSON round trip is no longer guaranteed. Marshaling drops unknown fields, adds zero values for absent required fields, and can omit explicit nulls or empty optional values. Keep the original payload if you need to preserve its JSON.

4. Stricter decoding can reject whole events or manifests

Values that were previously ignored or accepted can now return errors:

• Input blocks: malformed input elements fail decoding of the input block and

... (truncated)

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

[0.34.0] - 2026-11-03

Huge thank you to Michal Mazurek (@​akfaew) for submitting a bunch of patches for this release.

Breaking changes — read before upgrading

[!WARNING] v0.34.0 includes breaking API, decoding, serialization, and event-dispatch changes.

Your code may fail to compile. Code that still compiles may decode, serialize, or route events differently. Malformed payloads can cause an entire Events API event to be rejected.

Review every item below before upgrading, including interfaces, mocks, custom event decoders, and stored payloads.

1. Retired user APIs have been removed

• SetUserAsActive and SetUserAsActiveContext are gone. Remove these calls. SetUserPresence still supports away and auto, but marking user as active is gone.
• GetUsersOptionPresence is gone. Remove it from GetUsers, GetUsersContext, and GetUsersPaginated calls. User-list requests no longer send the retired presence parameter. Use GetUserPresence or GetUserPresenceContext for individual presence checks.

2. Team-info method signatures have changed

GetTeamInfo, GetTeamInfoContext, GetOtherTeamInfo, and GetOtherTeamInfoContext now accept ...GetTeamInfoOption. Update interfaces, mocks, and assigned function types to include the variadic parameter. Existing direct calls remain valid.

3. Auth-provider blocks have a new concrete type and lose raw JSON

[!NOTE] This is a brand new block. For now experimental as it doesn't yet appear in the slack docs but is already part of their official node sdk.

• auth_provider blocks now decode as *AuthProviderBlock, replacing *UnknownBlock. Update type assertions and type switches.

An unchanged JSON round trip is no longer guaranteed. Marshaling drops unknown fields, adds zero values for absent required fields, and can omit explicit nulls or empty optional values. Keep the original payload if you need to preserve its JSON.

4. Stricter decoding can reject whole events or manifests

Values that were previously ignored or accepted can now return errors:

... (truncated)

• acf69fb chore: release v0.34.0
• 7116a85 refactor: return the empty response error JSON directly
• b652660 refactor: return block marshaling results directly
• db5726f refactor: simplify interaction callback state marshaling
• 68456ec feat(auth)!: add standardized app authentication (#1679)
• 0fb6b11 feat(team)!: report slackbot availability (#1680)
• 59e8c35 fix(socketmode): dispatch outer events by type (#1683)
• f6237c6 fix(messages): preserve display_as_bot values (#1682)
• abd7ce4 test(conversations): pin latest and oldest on history requests (#1684)
• 1a85115 feat(canvases): retrieve canvas content (#1681)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions