This repository has been archived by the owner on Apr 24, 2022. It is now read-only.
Upgrade kurasuta: 2.2.0 → 3.0.2 (major) #262
Open
Conversation
This file contains 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ kurasuta (2.2.0 → 3.0.2) · Repo
Release Notes
3.0.2
3.0.1
3.0.0
2.2.3
2.2.2
2.2.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 38 commits:
[Release]: Release 3.0.2[Feat]: upgrade to use discord api v9 for fetching session endpoint[Fix]: Typing issues on latest versions[Deps]: update all packages to latest version & pin eslint configfix: replaced use of DjsUtil#delayFor (#474)[Release] Release 3.0.1[Fix] downgrade node-fetch to stable release[Chore] add .github to npmignore[Release] Release 3.0.0[Fix] try/catch error type check[Fix] discord.js on & once return type[Fix] typescript usage with nodejs cluster module[Chore]: update marine esline config usage & ignore comma-dangle rule[Deps]: remove not needed dev dep, update lockfile[Chore]: ignore .history in npm publish & git[Feat] Update to use discord.js v13 (#450)[Deps] Bump @types/ws from 7.4.2 to 7.4.4 (#408)[Deps] Bump @types/node from 14.14.43 to 15.0.1 (#405)Bump @types/ws from 7.4.0 to 7.4.2 (#404)[Chore] Upgrade to GitHub-native Dependabot (#406)[Chore] update prepare script[Release] Release 2.2.3[Feat] use http api v8[Deps] Bump dependency versions[Fix] shardCount default value can be undefined[Release] Release 2.2.2[Deps] Bump dependency versions[Fix] Ensure that options have correct types[Style] use singlequotes[Release] Release 2.2.1[Chore] eslint & typings fixes[Deps] Bump deps[Fix] Pass the original env to the child processes as well[Deps] Bump @typescript-eslint/parser from 3.10.1 to 4.0.1 (#381)[Deps] Bump @typescript-eslint/eslint-plugin from 3.10.1 to 4.0.0 (#380)[Deps] Bump typescript from 3.9.7 to 4.0.2 (#377)[Deps] Update eslint-config-marine to v7.2.0[Chore] Don't publish lockfileDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands