dependabot[bot] commented 4 weeks ago

Bumps Swashbuckle.AspNetCore from 6.8.1 to 6.9.0.

Release notes

Sourced from Swashbuckle.AspNetCore's releases.

v6.9.0

What's Changed

Generate Properties whenever there are objects without schema(Not onl… by @jgarciadelanoceda in domaindrivendev/Swashbuckle.AspNetCore#3095

fix: Pass props to multi targeting by @xC0dex in domaindrivendev/Swashbuckle.AspNetCore#3107

Types with TryParse must be set with type string by @jgarciadelanoceda in domaindrivendev/Swashbuckle.AspNetCore#3108

Add native AoT support for ReDoc by @martincostello in domaindrivendev/Swashbuckle.AspNetCore#3088

New Contributors

@xC0dex made their first contribution in domaindrivendev/Swashbuckle.AspNetCore#3107

Full Changelog: https://github.com/domaindrivendev/Swashbuckle.AspNetCore/compare/v6.8.1...v6.9.0

Commits

92ba260 Bump version (#3110)
0abed87 Merge pull request #3088 from martincostello/redoc-native-aot
349ba38 Types with TryParse must be set with type string (#3108)
a42d8c9 Pass props to multi-targeting (#3107)
d11913e Update .NET SDK (#3104)
683b8ee Bump actions/checkout from 4.2.0 to 4.2.1 (#3101)
fdc1ed4 Bump github/codeql-action from 3.26.10 to 3.26.12 (#3103)
ee9b319 Bump actions/cache from 4.0.2 to 4.1.1 (#3102)
9693037 Bump actions/upload-artifact from 4.4.0 to 4.4.2 (#3100)
c051ca6 Generate properties for objects without schema (#3095)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @guibranco.

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)

dependabot[bot] commented 4 weeks ago

The following labels could not be found: nuget, packages, .NET, dependencies.

korbit-ai[bot] commented 4 weeks ago

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

gooroo-dev[bot] commented 4 weeks ago

Please double check the following review of the pull request:

Issues counts

🐞Mistake	🤪Typo	🚨Security	🚀Performance	💪Best Practices	📖Readability	❓Others
0	0	0	0	0	0	0

Changes in the diff

🛠️ No changes in the code were detected as the diff is empty.

Identified Issues

Since the diff is empty, there are no identified issues to report.

Explanation of Identified Issues

There are no identified issues to explain due to the absence of changes in the diff.

Code to Address Issues

No code is required to address issues as there are no issues identified.

Explanation of the Fix

No explanation is needed as there are no fixes required.

Missing Tests

No tests are missing as there are no changes in the code to test.

Summon me to re-review when updated! Yours, Gooroo.dev React or reply to keep the conversation going!

semanticdiff-com[bot] commented 4 weeks ago

Review changes with SemanticDiff.

pr-code-reviewer[bot] commented 4 weeks ago

:wave: Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

codara-ai-code-review[bot] commented 4 weeks ago

Potential issues, bugs, and flaws that can introduce unwanted behavior:

Version Compatibility - /Directory.Packages.props - Upgrading Swashbuckle.AspNetCore from version 6.8.1 to 6.9.0 may introduce breaking changes or deprecations. Ensure that your code base is compatible with the new version to avoid runtime issues.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency:

Dependency Audit - /Directory.Packages.props - After updating the version of Swashbuckle.AspNetCore, conduct a thorough audit of the release notes and migration guides for version 6.9.0. This will help confirm that no critical changes impact the functionality of your application.
Update Testing Strategy - /Directory.Packages.props - With the update to Swashbuckle.AspNetCore, consider adding or updating unit and integration tests to ensure the new behavior aligns with expected outcomes, especially if there are any API changes in the new version.
Documentation Update - /Directory.Packages.props - Document the reason for the upgrade in your project notes or README files, including any known issues from the previous version and changes to be aware of in the new version. This aids in maintaining clarity for future developers.

instapr[bot] commented 4 weeks ago

Feedback:

The PR successfully bumps Swashbuckle.AspNetCore from 6.8.1 to 6.9.0. The changes look good to merge.

Make sure to test the application thoroughly post-merge to ensure the updated dependency works as expected.

Once you have completed testing, feel free to merge this PR.

Thank you!

sourcery-ai[bot] commented 4 weeks ago

🧙 Sourcery has finished reviewing your pull request!

Tips and commands

#### Interacting with Sourcery - **Trigger a new review:** Comment `@sourcery-ai review` on the pull request. - **Continue discussions:** Reply directly to Sourcery's review comments. - **Generate a GitHub issue from a review comment:** Ask Sourcery to create an issue from a review comment by replying to it. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a title at any time. - **Generate a pull request summary:** Write `@sourcery-ai summary` anywhere in the pull request body to generate a PR summary at any time. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) to: - Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others. - Change the review language. - Add, remove or edit custom review instructions. - Adjust other review settings. #### Getting Help - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).

github-actions[bot] commented 4 weeks ago

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

```txt 12:36PM INF scanning for exposed secrets... 12:36PM INF 132 commits scanned. 12:36PM INF scan completed in 81.5ms 12:36PM INF no leaks found ```