Nexus Repository End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 3.97.2-02

Nexus Repository end of life (EOL) and end of support (EOS) dates: 53 Nexus Repository versions have reached EOL, including Nexus Repository 3.80 (EOL date: Nov 06, 2026) — no longer receiving security updates or patches. Nexus Repository 3.84 reaches its End of Support date on Mar 09, 2027 — plan your upgrade path now. Nexus Repository 3.97.2-02 is the current supported release, with support through Apr 14, 2028 — 15 versions in active support. Also see Dependency-Track EOSL dates for related end-of-life information.

Nexus Repository end of life dates timeline — release schedule chart of the 8 most recent Nexus Repository versions, mapping active support and security support windows against their EOL dates
Nexus Repository end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Nexus Repository releases of 70 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Nexus Repository EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Nexus Repository Releases - Active EOS/EOSL Support (15)

Release Released Extended Maintenance Full Support Latest
3.97 (4 weeks and 1 day ago) (in 1 year and 5 months) (in 11 months) 3.97.2-02 (2 weeks and 6 days ago)
3.96 (2 months ago) (in 1 year and 3 months) (in 9 months) 3.96.4-01 (1 month and 1 week ago)
3.95 (3 months ago) (in 1 year and 2 months) (in 8 months) 3.95.4-01 (2 months ago)
3.94 (4 months ago) (in 1 year and 1 month) (in 7 months) 3.94.2-01 (2 months ago)
3.93 (5 months ago) (in 1 year) (in 6 months) 3.93.2-01 (4 months ago)
3.92 (6 months ago) (in 11 months) (in 5 months) 3.92.3-01 (5 months ago)
3.91 (7 months ago) (in 10 months) (in 4 months) 3.91.1-04 (6 months ago)
3.90 (8 months ago) (in 9 months) (in 3 months) 3.90.5-01 (2 months ago)
3.89 (9 months ago) (in 8 months) (in 2 months) 3.89.1-02 (9 months ago)
3.88 (9 months ago) (in 8 months) (in 2 months) 3.88.0-08 (9 months ago)
3.87 (11 months ago) (in 6 months) (in 2 weeks and 6 days) 3.87.2-01 (9 months ago)
3.85 (1 year and 1 month ago) (in 4 months) (1 month and 5 days ago) 3.85.1-01 (9 months ago)
3.83 (1 year and 3 months ago) (in 3 months) (3 months ago) 3.83.2-01 (1 year and 2 months ago)
3.82 (1 year and 4 months ago) (in 1 month and 4 weeks) (4 months ago) 3.82.1-08 (1 year and 2 months ago)
3.81 (1 year and 5 months ago) (in 4 weeks) (5 months ago) 3.81.1-01 (1 year and 5 months ago)

Nexus Repository Releases Nearing End of Life - Support Ending Soon (2)

Important: The following Nexus Repository releases will reach End of Life (EOL) within 6 months. Plan your migration to a supported release to ensure continued security updates and support.
Release Released Extended Maintenance Full Support Latest
3.84 (1 year and 2 months ago) (in 3 months) (2 months ago) 3.84.2-01 (9 months ago)
3.86 (1 year ago) (in 5 months) (1 week ago) 3.86.3-01 (9 months ago)

Nexus Repository End of Life (EOL) Releases - No Longer Supported (53)

Release Released Extended Maintenance Full Support Latest
3.80 (1 year and 6 months ago) (6 days ago) (6 months ago) 3.80.0-06 (1 year and 6 months ago)
3.79 (1 year and 7 months ago) (1 month and 1 week ago) (7 months ago) 3.79.1-04 (1 year and 7 months ago)
3.78 (1 year and 8 months ago) (2 months ago) (8 months ago) 3.78.2-04 (1 year and 7 months ago)
3.77 (1 year and 9 months ago) (3 months ago) (9 months ago) 3.77.2-02 (1 year and 8 months ago)
3.76 (1 year and 10 months ago) (4 months ago) (10 months ago) 3.76.1-01 (1 year and 9 months ago)
3.75 (1 year and 11 months ago) (5 months ago) (11 months ago) 3.75.1-01 (1 year and 11 months ago)
3.74 (2 years ago) (6 months ago) (1 year ago) 3.74.0-05 (2 years ago)
3.73 (2 years and 1 month ago) (7 months ago) (1 year and 1 month ago) 3.73.0-12 (2 years and 1 month ago)
3.72 (2 years and 2 months ago) (8 months ago) (1 year and 2 months ago) 3.72.0-04 (2 years and 2 months ago)
3.71 (2 years and 3 months ago) (9 months ago) (1 year and 3 months ago) 3.71.0-06 (2 years and 3 months ago)
3.70 (Latest for OrientDB) (2 years and 4 months ago) (10 months ago) (1 year and 4 months ago) 3.70.4-02 (1 year and 8 months ago)
3.69 (2 years and 5 months ago) (11 months ago) (1 year and 5 months ago) 3.69.0-02 (2 years and 5 months ago)
3.68 (2 years and 6 months ago) (1 year ago) (1 year and 6 months ago) 3.68.1-02 (2 years and 5 months ago)
3.67 (2 years and 7 months ago) (1 year and 1 month ago) (1 year and 7 months ago) 3.67.1-01 (2 years and 7 months ago)
3.66 (2 years and 8 months ago) (1 year and 2 months ago) (1 year and 8 months ago) 3.66.0-02 (2 years and 8 months ago)
3.65 (2 years and 9 months ago) (1 year and 3 months ago) (1 year and 9 months ago) 3.65.0-02 (2 years and 9 months ago)
3.64 (2 years and 10 months ago) (1 year and 4 months ago) (1 year and 10 months ago) 3.64.0-04 (2 years and 9 months ago)
3.63 (2 years and 11 months ago) (1 year and 5 months ago) (1 year and 11 months ago) 3.63.0-01 (2 years and 11 months ago)
3.62 (3 years ago) (1 year and 6 months ago) (2 years ago) 3.62.0-01 (3 years ago)
3.61 (3 years and 1 month ago) (1 year and 7 months ago) (2 years and 1 month ago) 3.61.0-02 (3 years and 1 month ago)
3.60 (3 years and 2 months ago) (1 year and 8 months ago) (2 years and 2 months ago) 3.60.0-02 (3 years and 2 months ago)
3.59 (3 years and 2 months ago) (1 year and 8 months ago) (2 years and 2 months ago) 3.59.0-01 (3 years and 2 months ago)
3.58 (3 years and 3 months ago) (1 year and 9 months ago) (2 years and 3 months ago) 3.58.1-02 (3 years and 3 months ago)
3.57 (3 years and 4 months ago) (1 year and 10 months ago) (2 years and 4 months ago) 3.57.1-03 (3 years and 3 months ago)
3.56 (3 years and 4 months ago) (1 year and 10 months ago) (2 years and 4 months ago) 3.56.0-01 (3 years and 4 months ago)
3.55 (3 years and 5 months ago) (1 year and 11 months ago) (2 years and 5 months ago) 3.55.0-01 (3 years and 5 months ago)
3.54 (3 years and 5 months ago) (1 year and 11 months ago) (2 years and 5 months ago) 3.54.1-01 (3 years and 5 months ago)
3.53 (3 years and 6 months ago) (2 years ago) (2 years and 6 months ago) 3.53.1-02 (3 years and 5 months ago)
3.52 (3 years and 6 months ago) (2 years ago) (2 years and 6 months ago) 3.52.0-01 (3 years and 6 months ago)
3.51 (3 years and 7 months ago) (2 years and 1 month ago) (2 years and 7 months ago) 3.51.0-01 (3 years and 7 months ago)
3.50 (3 years and 7 months ago) (2 years and 1 month ago) (2 years and 7 months ago) 3.50.0-01 (3 years and 7 months ago)
3.49 (3 years and 7 months ago) (2 years and 2 months ago) (2 years and 7 months ago) 3.49.0-02 (3 years and 8 months ago)
3.48 (3 years and 8 months ago) (2 years and 2 months ago) (2 years and 8 months ago) 3.48.0-01 (3 years and 8 months ago)
3.47 (3 years and 9 months ago) (2 years and 3 months ago) (2 years and 9 months ago) 3.47.1-01 (3 years and 8 months ago)
3.46 (3 years and 9 months ago) (2 years and 3 months ago) (2 years and 9 months ago) 3.46.0-01 (3 years and 9 months ago)
3.45 (3 years and 10 months ago) (2 years and 4 months ago) (2 years and 10 months ago) 3.45.1 (3 years and 9 months ago)
3.44 (3 years and 10 months ago) (2 years and 5 months ago) (2 years and 10 months ago) 3.44.0-01 (3 years and 10 months ago)
3.43 (4 years ago) (2 years and 6 months ago) (3 years ago) 3.43.0-01 (4 years ago)
3.42 (4 years and 1 month ago) (2 years and 7 months ago) (3 years and 1 month ago) 3.42.0-01 (4 years and 1 month ago)
3.41 (4 years and 3 months ago) (2 years and 9 months ago) (3 years and 3 months ago) 3.41.1-01 (4 years and 2 months ago)
3.40 (4 years and 4 months ago) (2 years and 10 months ago) (3 years and 3 months ago) 3.40.1-01 (4 years and 4 months ago)
3.39 (4 years and 5 months ago) (2 years and 11 months ago) (3 years and 3 months ago) 3.39.0-01 (4 years and 5 months ago)
3.38 (4 years and 8 months ago) (3 years and 1 month ago) (3 years and 3 months ago) 3.38.1-01 (4 years and 7 months ago)
3.37 (4 years and 11 months ago) (3 years and 5 months ago) — 3.37.3-02 (4 years and 10 months ago)
3.36 (5 years ago) (3 years and 6 months ago) — 3.36.0-01 (5 years ago)
3.35 (5 years ago) (3 years and 6 months ago) — 3.35.0-02 (5 years and 1 month ago)
3.34 (5 years and 2 months ago) (3 years and 8 months ago) — 3.34.1-01 (5 years and 1 month ago)
3.33 (5 years and 3 months ago) (3 years and 9 months ago) — 3.33.1-01 (5 years and 2 months ago)
3.32 (5 years and 4 months ago) (3 years and 10 months ago) — 3.32.1 (4 years and 10 months ago)
3.31 (5 years and 4 months ago) (3 years and 10 months ago) — 3.31.1-01 (5 years and 4 months ago)
3.30 (5 years and 8 months ago) (4 years and 2 months ago) — 3.30.1-01 (5 years and 6 months ago)
3.29 (5 years and 11 months ago) (4 years and 5 months ago) — 3.29.2-02 (5 years and 10 months ago)
2 (9 years and 7 months ago) (1 year and 4 months ago) — 2.15.2-03 (1 year and 11 months ago)

If you run Sonatype's Nexus Repository end of life checks by hand, you already know the question is never "does it still start?" but "does anyone still patch it?" This repository manager stores Docker images, Java packages, npm modules and other artifact formats, so a version that has aged out of the product development lifecycle (PDLC) leaves your whole build chain exposed. Here is how the sunset schedule works and what to do before your version reaches it. This page covers the Sonatype software, not Cisco Nexus switches.

How the Nexus Repository 3 Lifecycle Moves Toward Sunset

Every Nexus Repository 3 release follows the same path, which Sonatype calls its PDLC. A version is generally available and fully supported for a term of one year after its release, and then it spends a further six months in extended maintenance. After that, sunsetting is complete and the version gets nothing more.

  • General availability: twelve months of full support, with fixes and new features reaching the version.
  • Extended maintenance: six more months, intended for critical fixes only while you plan an upgrade.
  • Sunset: the version leaves the schedule entirely.

The clock starts at the first major release of a version line, such as 3.80.0, not at each later patch release. Patch builds like 3.80.1 move through the stages on the original schedule, so a late patch does not buy extra time.

Full Support and the Sunset Date Formula

You can work out any sunset date yourself from the initial release date. Add twelve months for full support and six for the extended window:

$$\text{sunset date} = \text{initial release date} + 12 \text{ months} + 6 \text{ months}$$

A line released on 14 October 2026, for example, stays supported until 14 October 2027 and is retired on 14 April 2028. Because a new release ships roughly every month, the oldest supported line is replaced at a steady pace.

Release Statuses by Version: Which Builds Are Sunsetted

The table below follows the versions status logic from the formula, with each status checked against today's date, 27 October 2026. Sonatype's own status page is the authority, and it may be a few weeks behind, so check when it was last updated. The entries show the dates that matter for a version.

VersionInitial releaseFull support endsSunset dateStatus
3.9714 Oct 202614 Oct 202714 Apr 2028General availability
3.905 Mar 20265 Mar 20275 Sep 2027General availability
3.857 Oct 20257 Oct 20267 Apr 2027Extended maintenance
3.806 May 20256 May 20266 Nov 2026Extended maintenance
3.791 Apr 20251 Apr 20261 Oct 2026Sunsetted
3.784 Mar 20254 Mar 20264 Sep 2026Sunsetted
3.774 Feb 20254 Feb 20264 Aug 2026Sunsetted
3.767 Jan 20257 Jan 20267 Jul 2026Sunsetted
3.753 Dec 20243 Dec 20253 Jun 2026Sunsetted
3.745 Nov 20245 Nov 20255 May 2026Sunsetted
3.7310 Oct 202410 Oct 202510 Apr 2026Sunsetted
3.724 Sep 20244 Sep 20254 Mar 2026Sunsetted

Read the release statuses from the bottom up: everything at or below 3.79 is already out of the schedule. Version 3.70 is the last line that still runs on OrientDB, and it too is past its sunset date. Version 3.80 is the next to go, on 6 November 2026.

Why a Sunset Nexus Repository Version Risks Security and Support

A sunset line stops receiving security fixes, and that is the real cost. An artifact repository sits between your developers and every dependency they pull, so an unpatched flaw in it is a flaw in your whole supply chain. An unpatched Nexus Repository keeps serving Docker, Java and npm requests as normal, but the software has lost its support and its safety net.

Expect these gaps once a version drops out:

  • No patch for newly disclosed vulnerabilities, however severe.
  • No maintenance help from the vendor when a build or an upgrade fails.
  • Growing trouble with newer clients, scanners and plugins that assume a current release.

Auditors also tend to treat unsupported software as a finding on its own, even when no exploit exists yet.

Nexus Repository Upgrade Options Before a Sunset Date

You have three realistic options when a version approaches retirement. Weigh the upgrade and substitution options against effort, because the cheapest path is rarely the one with the fewest steps.

  1. Upgrade in place to a current line. Back up your blob stores and database first, and check the release notes for changed requirements.
  2. Migrate to a fresh instance, which suits teams that also want to change the database or hosting at the same time.
  3. Replace the repository manager entirely, which is a larger project that only pays off if the current tool no longer fits.

Before choosing, ask which database your instance uses (OrientDB, H2 or PostgreSQL), how large your blob stores are, and which clients and formats depend on it. Those answers usually point to the in-place upgrade.

Stay on Extended Maintenance Only as a Bridge

For Nexus Repository 3, the six-month extended window ending at the sunset date is a runway, not a home. Use it to rehearse the upgrade in a staging copy, not to defer the decision until the final week.

Planning for Nexus Repository End of Life Before It Arrives

Treat the sunset date as a project deadline with a buffer. Work backward from the sunset date: a rehearsal, a change window, a rollback plan and a communication to every team that publishes or pulls artifacts. Teams on a monthly-release cadence often find that upgrading every few months is easier than one big jump after two years.

Start by listing which repositories carry Docker, Java and npm traffic, because those are the ones developers notice first when something breaks. Then confirm the target version supports your database choice and plan the cutover for a quiet day.

Can You Keep Running a Sunsetted Version?

Technically yes, because nothing switches off on the sunset date. In practice you carry the risk yourself, with no vendor patches and no fixes if something breaks, so the upgrade is the better course.

EOL dates of related software products