endoflife.ai
GitHub Enterprise Server EOL Watch How we verify

GitHub Enterprise Server 3.19 End of Life: December 9, 2026

By Scott Bissett  ·  Published: November 18, 2026  ·  EOL Watch — upcoming end of life  ·  Read at GitHub's releases page, the 3.19 and 3.18 documentation banners, GitHub's upgrade requirements and our tracked GitHub Enterprise Server data

GitHub Enterprise Server 3.19 reaches its closing down date on December 9, 2026. GitHub's releases page lists that day for 3.19, and the banner on the 3.19 documentation says the version will be discontinued then: “Discontinued releases are not supported. No patch releases will be made, even for critical security issues.” Three later releases stay supported: 3.20 until March 17, 2027, 3.21 until June 11, 2027 and 3.22 until September 8, 2027.

The rule that shapes your route. GitHub's upgrade requirements say: “You must upgrade from a feature release that's at most two releases behind. For example, to upgrade to GitHub Enterprise 3.22, you must be on GitHub Enterprise 3.21 or 3.20.” An instance on 3.19 is three feature releases behind 3.22, so by GitHub's own example it does not reach 3.22 in one upgrade.
Quick answer: The GitHub Enterprise Server 3.19 end-of-life (EOL) date is December 9, 2026. Every GitHub Enterprise Server version's release and end-of-support date is on the GitHub Enterprise Server lifecycle page.

What the closing down date means

“Closing down date” is GitHub's term. It is the heading of a column on the releases page, next to a column headed “Supported”. The releases page does not define the term in a sentence of its own. What it does say is this: “GitHub supports at least the four most recent feature releases. We provide documentation for both supported and unsupported versions of GitHub Enterprise Server. We do not maintain or update the documentation for unsupported versions.”

The plain statement is in the banner GitHub shows on the 3.19 documentation. It reads “This version of GitHub Enterprise Server will be discontinued on” December 9, 2026, and continues: “Discontinued releases are not supported. No patch releases will be made, even for critical security issues.” So the closing down date is the day two things end for 3.19: GitHub's support, and patch releases, security fixes included.

GitHub Enterprise Server 3.18 shows what the day after looks like. Its closing down date was October 16, 2026. The releases page now marks 3.18 as not supported, and the banner on the 3.18 documentation says the version “was discontinued” on that day.

What GitHub's pages do not say. The pages we read do not say that a running 3.19 instance stops working on its closing down date. What GitHub says ends is support and patch releases. We are not adding to that: an instance left on 3.19 after the date is on a release GitHub has said it will not patch.
Running GitHub Enterprise Server past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers GitHub Enterprise Server is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

The four supported releases

These rows are GitHub's releases page, which we read for this guide and which our GitHub Enterprise Server page carries in full. The status column is GitHub's own “Supported” column.

ReleaseReleasedClosing down dateGitHub's status
GitHub Enterprise Server 3.22September 8, 2026September 8, 2027Supported
GitHub Enterprise Server 3.21June 11, 2026June 11, 2027Supported
GitHub Enterprise Server 3.20March 17, 2026March 17, 2027Supported
GitHub Enterprise Server 3.19December 9, 2025December 9, 2026Supported

The page listed nothing newer than 3.22 when we read it. In each of these four rows the closing down date is the first anniversary of the release day. That is a pattern in the rows, not a rule GitHub states on the page: 3.18 was released on October 14, 2025 and its closing down date was October 16, 2026. Plan against the day GitHub prints for your release, not against a rule of thumb.

The upgrade path GitHub documents

GitHub documents one requirement and one recommendation that together decide the route from 3.19.

The requirement. “You must upgrade from a feature release that's at most two releases behind. For example, to upgrade to GitHub Enterprise 3.22, you must be on GitHub Enterprise 3.21 or 3.20.” Applied to 3.19, that rule puts 3.20 and 3.21 within reach of one upgrade, and puts 3.22 out of reach of one upgrade. The example is GitHub's, as the page stood when we read it.

The recommendation. “Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from GitHub Enterprise 3.20 to 3.21 to 3.22, you could upgrade from GitHub Enterprise 3.20 to 3.22. Use the Upgrade assistant to find the upgrade path from your current release version.”

Read together, they give a 3.19 instance two destinations. Under the rule it can move to 3.21 in one upgrade and stay supported until June 11, 2027. Or it can move to 3.20 or 3.21 first and then to 3.22, which is supported until September 8, 2027. A move to 3.20 alone buys the least time: 3.20 is the next release to close, on March 17, 2027.

We have not run the Upgrade assistant for any instance, and we are not naming the exact packages or steps for yours. GitHub's tool takes the release you are on and returns the path, and it is the authority. GitHub's overview of the upgrade process adds two facts that matter for scheduling: “You are responsible for upgrades to your instance,” and “To upgrade to a feature release, you must use an upgrade package.”

What to do before the closing down date

The quoted words in each step are GitHub's, from its upgrade requirements and its overview of the upgrade process.

  1. Get your path from GitHub. Confirm the feature release and patch release your instance runs, then follow GitHub's line: “Use the Upgrade assistant to find the upgrade path from your current release version.”
  2. Check the packages exist for you. “Upgrade packages are available at enterprise.github.com for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade.”
  3. Pick the newest patch of your target. “Use the latest patch release when upgrading.”
  4. Rehearse it. “Use a staging instance to test the upgrade steps.”
  5. Protect the data. “Take a snapshot before upgrading your virtual machine,” and “Ensure you have a recent, successful backup of your instance.”
  6. Check capacity. “You must perform a capacity check.” The overview adds a check that the instance's “data disk is at least 15% free.”
  7. Save your firewall rules. GitHub tells administrators to keep a copy of all custom firewall rules, “as customized rules will not persist post-upgrade.”

Until the upgrade is done, keep 3.19 patched. GitHub publishes patch releases for supported feature releases, and the 3.19 release notes list each one. After December 9, 2026 GitHub's banner says there will be none.

Frequently Asked Questions

When does GitHub Enterprise Server 3.19 reach end of life?

GitHub Enterprise Server 3.19 reaches its closing down date on December 9, 2026. That is the day GitHub's releases page lists for 3.19, and the banner on the 3.19 documentation says the version will be discontinued then. GitHub's own words are closing down date and discontinued, not end of life. 3.19 was released on December 9, 2025.

What happens after the GitHub Enterprise Server 3.19 closing down date?

GitHub's banner on the 3.19 documentation says discontinued releases are not supported and that no patch releases will be made, even for critical security issues. The releases page adds that GitHub does not maintain or update the documentation for unsupported versions. The pages we read do not say that a running instance stops working on that day.

Which GitHub Enterprise Server versions are supported after 3.19?

GitHub's releases page lists three later releases as supported: 3.20 with a closing down date of March 17, 2027, 3.21 with June 11, 2027, and 3.22 with September 8, 2027. GitHub says it supports at least the four most recent feature releases. The page listed nothing newer than 3.22 when we read it for this guide.

Can I upgrade from GitHub Enterprise Server 3.19 directly to 3.22?

Not by GitHub's stated rule. Its upgrade requirements say you must upgrade from a feature release that is at most two releases behind, and give the example that to upgrade to 3.22 you must be on 3.21 or 3.20. From 3.19 that leaves 3.20 or 3.21 as the first step. GitHub tells administrators to use its Upgrade assistant to find the path from their current release version; check it for your instance before you plan the work.

Is GitHub Enterprise Server 3.18 still supported?

No. GitHub's releases page marks 3.18 as not supported, with a closing down date of October 16, 2026, and the banner on the 3.18 documentation says the version was discontinued on that day. 3.19 is the next release to reach its closing down date.

Related

© 2026 endoflife.ai · How we verify our dates · API · About