Bump org.jline:jline from 3.30.5 to 3.30.6 in /test/fixtures/hdfs-fixture

[dependabot]

Bumps org.jline:jline from 3.30.5 to 3.30.6.

Release notes

Sourced from org.jline:jline's releases.

3.30.6

🐛 Bug Fixes

• Optimize Display performance and fix terminal capability usage (#1422) @​gnodet

Commits

• 06618a4 [maven-release-plugin] prepare release jline-3.30.6
• 140f9b1 Upgrade to njord 0.8.3
• b0c6185 Optimize Display performance and fix terminal capability usage (#1421) (#1422)
• ac4211d Set version to 3.30.6-SNAPSHOT
• See full diff 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 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 <dependency name> 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)

Summary by CodeRabbit

• Chores
  • Bumped test fixture dependency org.jline:jline from 3.30.5 to 3.30.6.
  • Updated changelog to reflect the dependency bump in the Unreleased 3.x Dependencies section.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Dependency version bump: org.jline:jline updated from 3.30.5 to 3.30.6 in the HDFS fixture Gradle build and mirrored in CHANGELOG.md.

Changes

Cohort / File(s)	Summary
Dependency Update test/fixtures/hdfs-fixture/build.gradle, CHANGELOG.md	Bumped dependency org.jline:jline from 3.30.5 → 3.30.6; CHANGELOG entry updated to reflect the bump.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• msfroh

Poem

🐰 A tiny hop, a version's slight,
From three-dot-thirty-oh-five to six so bright,
A gradle nudge, a changelog note,
The fixture hops and stays afloat.

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description lacks the required template structure (Description, Related Issues, Check List sections). It only contains Dependabot-generated release notes and metadata without the expected format.	Restructure the description to include: a concise Description section explaining the change, a Related Issues section (if applicable), and a Check List with applicable items. Consider whether testing is needed for this dependency bump.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: a dependency version bump for org.jline:jline from 3.30.5 to 3.30.6 in the specified directory.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 993a9ff and 7f8add8.

📒 Files selected for processing (1)

• CHANGELOG.md

🚧 Files skipped from review as they are similar to previous changes (1)

• CHANGELOG.md

⏰ 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: precommit (21, windows-latest)
• GitHub Check: precommit (25, windows-latest)
• GitHub Check: precommit (21, macos-15)
• GitHub Check: precommit (21, windows-2025, true)
• GitHub Check: precommit (21, macos-15-intel)
• GitHub Check: precommit (25, macos-15)
• GitHub Check: precommit (25, macos-15-intel)
• GitHub Check: precommit (25, ubuntu-24.04-arm)
• GitHub Check: precommit (25, ubuntu-latest)
• GitHub Check: precommit (21, ubuntu-latest)
• GitHub Check: precommit (21, ubuntu-24.04-arm)
• GitHub Check: assemble (25, ubuntu-24.04-arm)
• GitHub Check: dependabot
• GitHub Check: assemble (21, windows-latest)
• GitHub Check: assemble (21, ubuntu-latest)
• GitHub Check: detect-breaking-change
• GitHub Check: assemble (25, ubuntu-latest)
• GitHub Check: Analyze (java)
• GitHub Check: assemble (21, ubuntu-24.04-arm)
• GitHub Check: assemble (25, windows-latest)

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

❌ Gradle check result for 993a9ff: 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?

[github-actions]

❌ Gradle check result for 7f8add8: 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?

[github-actions]

❌ Gradle check result for 7f8add8: 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?

[github-actions]

❌ Gradle check result for 7f8add8: 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?

[github-actions]

❌ Gradle check result for 7f8add8: 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?

[github-actions]

❌ Gradle check result for 7f8add8: 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?

[github-actions]

❌ Gradle check result for 7f8add8: 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?

[cwperks]

Third time I've seen this error today:

> Task :test:fixtures:azure-fixture:composeBuild
The command '/bin/sh -c apt-get install -qqy openjdk-21-jre-headless' returned a non-zero code: 100
Service 'azure-fixture' failed to build : Build failed

Taking a deeper look

[github-actions]

✅ Gradle check result for 7f8add8: SUCCESS

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.19%. Comparing base (d866be8) to head (7f8add8).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #20369      +/-   ##
============================================
- Coverage     73.30%   73.19%   -0.11%     
+ Complexity    71777    71705      -72     
============================================
  Files          5784     5784              
  Lines        328141   328145       +4     
  Branches      47269    47270       +1     
============================================
- Hits         240531   240174     -357     
- Misses        68329    68656     +327     
- Partials      19281    19315      +34     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.