search

2lambda123 / michelin-kstreamplify

Apache License 2.0
0 stars 0 forks source link

Bump org.springframework.boot:spring-boot-dependencies from 3.3.4 to 3.3.5 #55

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps org.springframework.boot:spring-boot-dependencies from 3.3.4 to 3.3.5.

Release notes

Sourced from org.springframework.boot:spring-boot-dependencies's releases.

v3.3.5

:lady_beetle: Bug Fixes

  • Running mvn spring-boot:run with classpaths that exceeds Windows' length limits leaves temporary files #42841
  • Report produced by ConditionReportApplicationContextFailureProcessor is always empty in a failed test #42785
  • Case-insensitive comparisons may be adversely affected by the user's locale #42735
  • DataSourceProperties#driverClassIsLoadable should not print a stacktrace to the error stream when it fails #42683
  • Some @ControllerEndpoint and @RestControllerEndpoint infrastructure remains undeprecated #42498
  • Auto-configuration for Rabbit Streams doesn't consider RabbitConnectionDetails #42490
  • ClassNotFoundException is thrown when loading protocol resolvers from ForkJoinPool task #42468
  • ActiveMQ Artemis Connection Factory creation fails in native image #42421
  • Duplicate meter binding when context contains multiple registries, none are primary, and one or more is a composite #42397

:notebook_with_decorative_cover: Documentation

  • Document that embedded Tomcat must be at least 10.1.25 #42849
  • Fix systemd example configuration #42805
  • Document that the exact behavior of the maximum HTTP request header size property is server-specific #42789
  • Clarify why @Primary is recommended when defining your own ObjectMapper that replaces JacksonAutoConfiguration's #42787
  • Polish javadoc for Binder#bindOrCreate(String, Class) #42778
  • Document that Tomcat's maxQueueCapacity need to be greater than 0 #42726
  • Remove stale link to jar-to-war getting started guide #42723
  • Fix typos and formatting errors in documentation #42718
  • Fix case used for examples in "Sanitize Sensitive Values" #42702
  • Fix Regex javadoc links #42685
  • Document how Map properties are bound from environment variables #42672
  • Improve classpath index documentation for reproducible builds #42643
  • Remove links to Spring Data GemFire #42596
  • Order alphabetically the sections in Common Application Properties #42520
  • Improve the javadoc describing when @ConditionalOn(Missing)Bean will infer the type to match #42505
  • Document how to handle MANIFEST.MF in native image with Maven #42476
  • Fix links to Micrometer reference doc #42467
  • Polish documentation #42454
  • Add Javadoc since for PrometheusScrapeEndpoint(PrometheusRegistry, Properties) #42406
  • Remove note about graceful shutdown with Tomcat requiring 9.0.33 or later as we now require 10.1.x #42382
  • Document support for Java 23 #42380
  • Improve documentation for CycloneDX integration #41506

:hammer: Dependency Upgrades

  • Prohibit upgrades to Undertow 2.3.18.Final #42756
  • Upgrade to CycloneDX Maven Plugin 2.8.2 #42631
  • Upgrade to GraphQL Java 22.3 #42757
  • Upgrade to Infinispan 15.0.10.Final #42632
  • Upgrade to Jaybird 5.0.6.java11 #42752
  • Upgrade to Jersey 3.1.9 #42633
  • Upgrade to Jetty 12.0.14 #42635
  • Upgrade to Jetty Reactive HTTPClient 4.0.8 #42634
  • Upgrade to jOOQ 3.19.14 #42818
  • Upgrade to JUnit Jupiter 5.10.5 #42637

... (truncated)

Commits
  • 2316ce6 Release v3.3.5
  • 02f6eb4 Merge branch '3.2.x' into 3.3.x
  • 728deaf Next development version (v3.2.12-SNAPSHOT)
  • 9ca6667 Merge branch '3.2.x' into 3.3.x
  • 9858b4b Fix release script
  • 2bf3e5a Document that embedded Tomcat must be 10.1.25 or later
  • 13e75dc Upgrade to Spring Integration 6.3.5
  • 131bbaf Merge branch '3.2.x' into 3.3.x
  • 83a3212 Use github.ref_name when deploying snapshots
  • 2d91385 Merge branch '3.2.x' into 3.3.x
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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 2 weeks ago

The following labels could not be found: dependencies.

sourcery-ai[bot] commented 2 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).
performance-testing-bot[bot] commented 2 weeks ago

Unable to locate .performanceTestingBot config file

korbit-ai[bot] commented 2 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.

cr-gpt[bot] commented 2 weeks ago

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

git-greetings[bot] commented 2 weeks ago

Thanks @dependabot[bot] for opening this PR!

For COLLABORATOR only :

git-greetings[bot] commented 2 weeks ago
PR Details of @dependabot[bot] in michelin-kstreamplify : OPEN CLOSED TOTAL
3 27 30
coderabbitai[bot] commented 2 weeks ago

[!IMPORTANT]

Review skipped

Bot user detected.

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.

🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@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 using 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. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
socket-security[bot] commented 2 weeks ago

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

Package New capabilities Transitives Size Publisher

🚮 Removed packages: maven/org.springframework.boot/spring-boot-dependencies@3.3.4

View full report↗︎

socket-security[bot] commented 2 weeks ago

🚨 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 NoteSourceCI
Critical CVE maven/org.scala-lang/scala-library@2.13.6 ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore maven/org.scala-lang/scala-library@2.13.6