Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency @sapphire/discord.js-utilities to v7 #329

Merged
merged 1 commit into from
Nov 12, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sapphire/discord.js-utilities (source) 6.1.0 -> 7.0.2 age adoption passing confidence

Release Notes

sapphiredev/utilities (@​sapphire/discord.js-utilities)

v7.0.2

Compare Source

🐛 Bug Fixes

  • discord.js-utilities: Output proper dist files (75fded2)
  • discord.js-utilities: Revised type-guards for thread channels (#​639) (62f14dc)

v7.0.1

Compare Source

🐛 Bug Fixes

🧪 Testing

  • Update vitest to coverage v8 (a4bc6e4)

v7.0.0

Compare Source

🏠 Refactor

  • PaginatedMessage: Cleaned up some internal type casting. (870252d)
  • PaginatedMessage: The callback union is removed from messages property. pages are always processed with resolvePage meaning they can never be a callback. (4407907)
  • PaginatedMessage: PaginatedMessageMessageOptionsUnion now omits components as it was not handled anyway. (d60b8e2)
  • PaginatedMessage: Allow PaginatedMessage actions run to be optional and instead get handled by Sapphire interaction-handlers (d87eede)
    • 💥 BREAKING CHANGE: updateCurrentPage components are now resolved from the actions property
      instead of the components property. This makes it consistent with all the other
      page manipulation methods
    • 💥 BREAKING CHANGE: Removed getComponents since it is effectively useless due to the above change.

🚀 Features

  • PaginatedMessage: Added utility functions for type-guarding action variants. (5c0ae46)

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/sapphire-discord.js-utilities-7.x branch from 36ec70a to 06fc3c2 Compare June 3, 2023 03:34
@renovate renovate bot force-pushed the renovate/sapphire-discord.js-utilities-7.x branch from 06fc3c2 to 1fcad4c Compare July 21, 2023 16:40
@renovate renovate bot force-pushed the renovate/sapphire-discord.js-utilities-7.x branch from 1fcad4c to 2291489 Compare August 5, 2023 04:10
@renovate renovate bot force-pushed the renovate/sapphire-discord.js-utilities-7.x branch 3 times, most recently from 1f574e7 to 409d275 Compare August 30, 2023 17:27
@renovate renovate bot force-pushed the renovate/sapphire-discord.js-utilities-7.x branch from 409d275 to 17dfdac Compare November 12, 2023 03:51
@BenSegal855 BenSegal855 merged commit 476b1f0 into dev Nov 12, 2023
4 of 5 checks passed
@renovate renovate bot deleted the renovate/sapphire-discord.js-utilities-7.x branch November 12, 2023 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant