Bump ch.qos.logback:logback-core from 1.5.27 to 1.5.32 in /test/fixtures/hdfs-fixture#20637
Conversation
Bumps [ch.qos.logback:logback-core](https://github.com/qos-ch/logback) from 1.5.27 to 1.5.32. - [Release notes](https://github.com/qos-ch/logback/releases) - [Commits](qos-ch/logback@v_1.5.27...v_1.5.32) --- updated-dependencies: - dependency-name: ch.qos.logback:logback-core dependency-version: 1.5.32 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughUpdates Logback dependency versions from 1.5.27 to 1.5.32 in the HDFS test fixture build configuration. Only version coordinates are modified with no changes to control flow or dependencies. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Comment |
Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@test/fixtures/hdfs-fixture/build.gradle`:
- Around line 82-83: The build.gradle change adds dependencies
"ch.qos.logback:logback-core:1.5.32" and "ch.qos.logback:logback-classic:1.5.32"
which are not confirmed on Maven Central; before merging either verify those
exact coordinates are published to Maven Central or point Gradle to a repository
that hosts them (or revert to the last known-good logback version). Update the
Gradle repositories to include a confirmed host if needed (or change the
dependency versions back) and confirm a successful Gradle resolution/build for
the symbols "ch.qos.logback:logback-core:1.5.32" and
"ch.qos.logback:logback-classic:1.5.32" before merging.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
test/fixtures/hdfs-fixture/build.gradle
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (21)
- GitHub Check: gradle-check
- GitHub Check: assemble (25, ubuntu-24.04-arm)
- GitHub Check: assemble (25, windows-latest)
- GitHub Check: assemble (25, ubuntu-latest)
- GitHub Check: assemble (21, ubuntu-latest)
- GitHub Check: assemble (21, windows-latest)
- GitHub Check: assemble (21, ubuntu-24.04-arm)
- GitHub Check: Analyze (java)
- GitHub Check: detect-breaking-change
- GitHub Check: precommit (25, ubuntu-latest)
- GitHub Check: dependabot
- GitHub Check: precommit (21, macos-15)
- GitHub Check: precommit (25, macos-15-intel)
- GitHub Check: precommit (21, windows-2025, true)
- GitHub Check: precommit (25, macos-15)
- GitHub Check: precommit (25, ubuntu-24.04-arm)
- GitHub Check: precommit (21, ubuntu-24.04-arm)
- GitHub Check: precommit (21, ubuntu-latest)
- GitHub Check: precommit (25, windows-latest)
- GitHub Check: precommit (21, macos-15-intel)
- GitHub Check: precommit (21, windows-latest)
|
❌ Gradle check result for f45771c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for f45771c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for f45771c: null Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for f45771c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for f45771c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Bumps ch.qos.logback:logback-core from 1.5.27 to 1.5.32.
Release notes
Sourced from ch.qos.logback:logback-core's releases.
Commits
e807335prepare release 1.5.32dc35d55fix logback-access/issues/34 by checking if dependency is a sub-model of the ...8e32278added simple test for appender definitiob via file inclusion834dbedstart work on 1.5.32-SNAPSHOT168e42fadd test to check that Logback SLF4J provider can be activateded45362prepare release 1.5.31609dae7fix missing META-INF directory7739739start work on 1.5.31-SNAPSHOT44164f1prepare release 1.5.309874f06test for top-file as a resource, introduced new module logback-classic-miscDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)