Update swagger-parser to 2.1.36

[xerial-bot]

About this PR

📦 Updates io.swagger.parser.v3:swagger-parser from 2.1.35 to 2.1.36

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "io.swagger.parser.v3", artifactId = "swagger-parser" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.swagger.parser.v3", artifactId = "swagger-parser" }
}]

^{labels: test-library-update}

[gemini-code-assist]

Summary of Changes

Hello @xerial-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a routine maintenance task: updating the swagger-parser test dependency to its latest patch version, 2.1.36. This ensures that the project's test suite benefits from any minor bug fixes or improvements introduced in the new swagger-parser release, maintaining compatibility and stability in the testing environment.

Highlights

• Dependency Update: The swagger-parser library has been updated from version 2.1.35 to 2.1.36.
• Scope of Change: This update specifically targets the Test scope, meaning it affects only the testing environment and not the production runtime.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Scala Steward, updates the swagger-parser test dependency from version 2.1.35 to 2.1.36. This is a beneficial maintenance update which includes updates to transitive dependencies like Jackson, potentially resolving security vulnerabilities. The change is confined to the test scope, so it has no impact on production code. While the version bump is correct, I've suggested a small improvement to define the version as a constant for better maintainability, consistent with how other dependencies are managed in this file.

[gemini-code-assist]

For consistency and better maintainability, it's a good practice to define dependency versions as vals at the top of the build.sbt file, as is done for other dependencies like AIRSPEC_VERSION, SLF4J_VERSION, etc. Please define a SWAGGER_PARSER_VERSION and use it here.

For example, you could add this near the other version definitions:

val SWAGGER_PARSER_VERSION = "2.1.36"

And then use it here.

        "io.swagger.parser.v3" % "swagger-parser" % SWAGGER_PARSER_VERSION % Test,