[Snyk] Upgrade @azure-tools/typespec-autorest from 0.42.1 to 0.43.0

[abdulrahman305]

Snyk has created this PR to upgrade @azure-tools/typespec-autorest from 0.42.1 to 0.43.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 12 versions ahead of your current version.

• The recommended version was released on a month ago.

Release notes

Package name: @azure-tools/typespec-autorest

• 0.43.0 - 2024-06-14
  

  @ azure-tools/typespec-autorest

  Bug Fixes

  • #923 When emitting version enum only include current version and mark with modelAsString: true
  • #902 Add support for new multipart constructs in http library
  • #432 Add support for tuple literals as default values

  Bump dependencies

  • #867 Update dependencies - May 2024

  Features

  • #955 Use emit-lro--options emitter option to control emission of x-ms-long-running-operation-options
  • #955 Add support for displaying lro options in typespec-autorest based on lro metadata
  • #972 Add API to programmatically get all the OpenAPI2 documents for all services at all versions in a spec
  • #811 Add dependency on typespec-azure-resource-manager to resolve the spec repo common types paths
  • #813 @ summary sets the title of definitions

  Breaking Changes

  • #473 Enums are not extensible by default anymore. Update to an extensible union union Foo {a: "a", b: "b", string}

  @ azure-tools/typespec-azure-core

  Bug Fixes

  • #693 Add new no-string-discriminator linter rule suggesting using an explicit extensible union as the discriminator kind.
  • #851 Convert OperationState enum to an open union

  Bump dependencies

  • #867 Update dependencies - May 2024

  Features

  • #955 Add override decorator @ useFinalStateVia for lro resolution when multiple resolution pathways exist
  • #707 Remove linter rules that are not relevant anymore: use-extensible-enum and no-fixed-enum-discriminator
  • #432 Add support for values

  @ azure-tools/typespec-azure-portal-core

  Bump dependencies

  • #867 Update dependencies - May 2024

  @ azure-tools/typespec-azure-resource-manager

  Bug Fixes

  • #998 Adding legacy v4 ManagedServiceIdentity model to avoid breaking changes in specs with mixed v3 and v4 common type reference
  • #955 Remove OpenAPI dependencies from ARM LRO templates and test LRO overrides
  • #929 Adding an overload parameter to ResourceNameParameter that allows name type to be set to string union type.
  • #860 Fix percentComplete property on OperationStatus should be a float not an int
  • #979 Make Resource Properties Bag Updatable

  Bump dependencies

  • #867 Update dependencies - May 2024

  Features

  • #811 Remove dependency on typespec-autorest emitter
  • #432 Add support for values

  @ azure-tools/typespec-client-generator-core

  Bug Fixes

  • #904 don't add constant value to generated name
  • #873 add description for created discriminator property
  • #947 support new typespec emitter naming rule
  • #930 expose enums on response headers
  • #962 refine logic of core model filtering
  • #950 remove duplicated types in TCGC
  • #936 enhance cross language definition id logic
  • #935 add read only logic to usage propagation

  Bump dependencies

  • #867 Update dependencies - May 2024

  Breaking Changes

  • #925 change default of .access on a model or enum to "public" instead of undefined
  • #870 return nullable types as a new type called SdkNullableType
• 0.43.0-dev.11 - 2024-06-11
• 0.43.0-dev.9 - 2024-06-07
• 0.43.0-dev.8 - 2024-06-04
• 0.43.0-dev.7 - 2024-05-25
• 0.43.0-dev.6 - 2024-05-24
• 0.43.0-dev.5 - 2024-05-21
• 0.43.0-dev.4 - 2024-05-20
• 0.43.0-dev.3 - 2024-05-15
• 0.43.0-dev.2 - 2024-05-09
• 0.43.0-dev.1 - 2024-05-08
• 0.43.0-dev.0 - 2024-05-08
• 0.42.1 - 2024-05-15

from @azure-tools/typespec-autorest GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[korbit-ai]

👋 I'm here to help you review your pull request. When you're ready for me to perform a review, you can comment anywhere on this pull request with this command: /korbit-review.

As a reminder, here are some helpful tips on how we can collaborate together:

• To have me re-scan your pull request, simply re-invoke the /korbit-review command in a new comment.
• You can interact with me by tagging @korbit-ai in any conversation in your pull requests.
• On any comment I make on your code, please leave a 👍 if it is helpful and a 👎 if it is unhelpful. This will help me learn and improve as we work together
• Lastly, to learn more, check out our Docs.

[codeautopilot]

Your organization has reached the subscribed usage limit. You can upgrade your account by purchasing a subscription at Stripe payment link

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 103.59%

Have feedback or need help?
Discord
Documentation
support@codeautopilot.com

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

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 Configuration 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.