Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

dependency updates for 4.x stopped in 2023?

Open
#9,760 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
documentation

Research direction

Start by reading the security and 4.x changelog pages linked in the issue, then verify the stated EOL date against the project's maintenance policy. The request is to clarify or correct the 4.x EOL information; done means the page accurately reflects the supported release and dependency-update policy. No source file or test is identified, so locating the documentation entry point will take some reading around.

Written by the indexing model from the issue text.

Description

bug

Dears,

First of all, let me thank you for the effort you put into okhttp!

Our project relies currently on 4.12.0 released in 2023: https://lysine.dev/okhttp/changelogs/changelog_4x/

I understand from https://lysine.dev/okhttp/security/security/ that EOL of 4.x is only in about one year in 2027.

At the same time, 5.x receives in its regular minor/patch releases dependency version bumps, that I do not see for 4.x since July 2023 (https://github.com/lysine-dev/okhttp/pull/7947).

I hear that questions are not for the Github bug tracker. So please read this as an issue request on possibly outdated EOL information on https://lysine.dev/okhttp/security/security/ 🙂 .

Dominant language
Kotlin
Stars
47.1k
Forks
9.3k
Avg merge
18h 18m
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lysine-dev/okhttp

All issues in lysine-dev/okhttp

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.