AspectOfJerry / JerryBot

Discord bot for personal use. Built on Discordjs v13.
https://bot.jerrydev.net
1 stars 0 forks source link

Bump axios and openai #153

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 11 months ago

Removes axios. It's no longer used after updating ancestor dependency openai. These dependencies need to be updated together.

Removes axios

Updates openai from 3.2.1 to 4.17.4

Release notes

Sourced from openai's releases.

v4.17.4

4.17.4 (2023-11-10)

Full Changelog: v4.17.3...v4.17.4

Chores

v4.17.3

4.17.3 (2023-11-09)

Full Changelog: v4.17.2...v4.17.3

v4.17.2

4.17.2 (2023-11-09)

Full Changelog: v4.17.1...v4.17.2

Chores

v4.17.1

4.17.1 (2023-11-09)

Full Changelog: v4.17.0...v4.17.1

Refactors

  • client: deprecate files.retrieveContent in favour of files.content (#474) (7c7bfc2)

v4.17.0

4.17.0 (2023-11-08)

Full Changelog: v4.16.2...v4.17.0

Features

Refactors

  • api: rename FunctionObject to FunctionDefinition (#470) (f3990c7)

v4.16.2

4.16.2 (2023-11-08)

Full Changelog: v4.16.1...v4.16.2

... (truncated)

Changelog

Sourced from openai's changelog.

4.17.4 (2023-11-10)

Full Changelog: v4.17.3...v4.17.4

Chores

4.17.3 (2023-11-09)

Full Changelog: v4.17.2...v4.17.3

4.17.2 (2023-11-09)

Full Changelog: v4.17.1...v4.17.2

Chores

4.17.1 (2023-11-09)

Full Changelog: v4.17.0...v4.17.1

Refactors

  • client: deprecate files.retrieveContent in favour of files.content (#474) (7c7bfc2)

4.17.0 (2023-11-08)

Full Changelog: v4.16.2...v4.17.0

Features

Refactors

  • api: rename FunctionObject to FunctionDefinition (#470) (f3990c7)

4.16.2 (2023-11-08)

Full Changelog: v4.16.1...v4.16.2

Bug Fixes

  • api: accidentally required params, add new models & other fixes (#463) (1cb403e)
  • api: update embedding response object type (#466) (53b7e25)
  • asssitant_deleted -> assistant_deleted (#452) (ef89bd7)

... (truncated)

Commits
  • 12de980 Merge pull request #483 from openai/release-please--branches--master--changes...
  • b8441a7 release: 4.17.4
  • 3013e8c chore(internal): update jest config (#482)
  • d2d0ce5 release: 4.17.3
  • d0e2c77 ci: fix deno version bump (#480)
  • 78ec255 Merge pull request #479 from openai/release-please--branches--master--changes...
  • 488d731 release: 4.17.2
  • 69913f3 chore(internal): bump deno version number (#478)
  • 03d1662 Merge pull request #475 from openai/release-please--branches--master--changes...
  • 0532117 release: 4.17.1
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by dschnurr-openai, a new releaser for openai since your current version.


You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options
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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/AspectOfJerry/JerryBot/network/alerts).

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

pull-request-quantifier-deprecated[bot] commented 10 months ago

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.


Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.