chore: 🐝 Update SDK - Generate TS SDK

[naelob]

SDK update

Based on:

• OpenAPI Doc
• Speakeasy CLI 1.335.0 (2.370.2) https://github.com/speakeasy-api/speakeasy

TYPESCRIPT CHANGELOG

responseFormat: 0.2.3 - 2024-03-27

🐛 Bug Fixes

• flat response format to work when operations contain empty responses (commit by @disintegrator)

core: 3.11.6 - 2024-07-09

🐛 Bug Fixes

• Use 0666 file mode for writing configuration and lock files (commit by @bflad)

defaultEnabledRetries: 0.1.0 - 2024-07-11

🐝 New Features

• always allow users to pass a retry policy when calling an SDK methods (commit by @disintegrator)

retries: 2.83.0 - 2024-02-12

🐝 New Features

• read retry-after header in typescriptv2 (commit by @ryan-timothy-albert)

globalSecurity: 2.82.9 - 2024-04-01

🐛 Bug Fixes

• TSv2 security compilation (commit by @chase-crumbaugh)

globalServerURLs: 2.82.4 - 2024-03-06

🔧 Chores

• expand server selection test coverage (commit by @2ynn)

constsAndDefaults: 0.1.5 - 2024-03-01

🐛 Bug Fixes

• null enums are coerced into null consts (commit by @disintegrator)

[rflihxyz]

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command	Blueprint environment
/qovery preview 783d0240-ec38-4387-a9a9-8e225f1bd3e1	dev
/qovery preview {all|UUID1,UUID2,...}	To preview multiple environments

---

This comment has been generated from Qovery AI 🤖.
Below, a word from its wisdom :

Take rest sometimes

[changeset-bot]

⚠️ No Changeset found

Latest commit: a6b2a97

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@typescript-eslint/[email protected]	Transitive: environment	+8	5.04 MB	jameshenry
npm/@typescript-eslint/[email protected]	Transitive: environment	+6	1.87 MB	jameshenry
npm/[email protected]	None	0	21.9 MB	typescript-bot

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Environment variable access	npm/[email protected]	Env Vars: PREFIX Location: Package overview	pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: LOCALAPPDATA Location: Package overview	pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: PREFIX Location: Package overview	pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: Location: Package overview	pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: name Location: Package overview	pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: APPDATA Location: Package overview	pnpm-lock.yaml	🚫
Environment variable access	npm/[email protected]	Env Vars: LOCALAPPDATA Location: Package overview	pnpm-lock.yaml	🚫
Mixed license	npm/[email protected]	License: BSD-3-Clause AND MIT	pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is a mixed license?

(Experimental) Package contains multiple licenses.

A new version of the package should be published that includes a single license. Consumers may seek clarification from the package author. Ensure that the license details are consistent across the LICENSE file, package.json license field and license details mentioned in the README.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]