Skip to content

Fix OKHTTP dependency inconsistency #863

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

larskristianhaga
Copy link
Contributor

@larskristianhaga larskristianhaga commented Jun 2, 2025

Pull Request

Following up on PR #856, that tried to fix the issue with dependency resolving to alpha version of the OKHTTP dependency.

Example repo that showcases that meilisearch-java:0.14.6 still resolves to OKHTTP 5.0.0-alpha.16.
https://github.com/larskristianhaga/Meilisearch-OKHTTP-dependency-crash-demo

What does this PR do?

  • Pinning OKHTTP version to 4.12.0, which is the same used as test scope.
  • Removed dependency selection rejection that did not work.

PR checklist

Please check if your PR fulfills the following requirements:

  • Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
  • Have you read the contributing guidelines?
  • Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Summary by CodeRabbit

  • Chores
    • Updated the okhttp dependency to a fixed version (4.12.0).
    • Removed restrictions that previously blocked pre-release dependency versions.

Copy link
Contributor

coderabbitai bot commented Jun 2, 2025

Walkthrough

The pull request removes the Gradle configuration that previously rejected pre-release dependency versions and updates the okhttp dependency from a version range to a fixed version 4.12.0. No changes were made to public APIs or exported entities.

Changes

File(s) Change Summary
build.gradle Removed pre-release version rejection strategy; fixed okhttp dependency version to 4.12.0

Possibly related PRs

Suggested labels

enhancement

Poem

A hop through the code, a leap through the grass,
Out with the filters—let all versions pass!
OkHttp stands steady, version fixed and true,
No more alpha or beta sneaking through.
With a twitch of my nose and a thump of my feet,
This build is now tidy, robust, and neat!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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 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 for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@larskristianhaga larskristianhaga changed the title Fix okhttp dependency inconsistency Fix OKHTTP dependency inconsistency Jun 2, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
build.gradle (1)

65-65: Centralize OkHttp version to avoid duplication
The testImplementation scope also hardcodes okhttp:4.12.0, mirroring the api declaration. Consider introducing an ext.okhttpVersion = '4.12.0' at the top of the file and referencing it in both places to reduce maintenance overhead and prevent drift.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b5a0705 and 7859b79.

📒 Files selected for processing (1)
  • build.gradle (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: integration-and-unit-tests
🔇 Additional comments (1)
build.gradle (1)

56-56:

❓ Verification inconclusive

Pin OkHttp dependency to stable release
Locking okhttp to 4.12.0 prevents pulling in the unintended 5.0.0-alpha artifacts, ensuring a consistent, stable client at both compile and runtime.

Please verify no other configurations or transitive dependencies resolve a different OkHttp version:


🏁 Script executed:

#!/bin/bash
# Ensure no alpha or RC versions of okhttp are pulled in
./gradlew dependencies --configuration runtimeClasspath | grep okhttp

Length of output: 261


Pin OkHttp dependency to stable release
Locking okhttp to 4.12.0 prevents pulling in unintended 5.0.0-alpha artifacts, ensuring a consistent, stable client at both compile and runtime.

The previous dependency check failed due to an invalid JAVA_HOME setting. To confirm no other configurations or transitive dependencies pull in a different OkHttp version, please:

• Ensure JAVA_HOME is set to a valid JDK installation.
• Re-run the dependencies check:

./gradlew dependencies --configuration runtimeClasspath | grep okhttp

@larskristianhaga
Copy link
Contributor Author

@brunoocasali tagging you since you worked on the last PR

Copy link
Member

@brunoocasali brunoocasali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bors merge

Copy link
Contributor

meili-bors bot commented Jun 2, 2025

Build succeeded:

  • linter
  • integration-and-unit-tests

@meili-bors meili-bors bot merged commit 5f56246 into meilisearch:main Jun 2, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants