Back to Yarp

YARP Roadmap

docs/roadmap.md

2.3.03.4 KB
Original Source

YARP Roadmap

Supported YARP versions

Latest releases

VersionRelease DateLatest Patch VersionEnd of Support
YARP 2.3February 27, 20252.3.0

End-of-life YARP versions

VersionReleased dateFinal Patch VersionEnd of support
YARP 2.2September 3, 20242.2.0August 27, 2025
YARP 2.1November 17, 20232.1.0March 3, 2025
YARP 2.0February 14, 20232.0.1May 17, 2024
YARP 1.1May 2, 20221.1.2August 14, 2023
YARP 1.0November 9, 20211.0.1November 2, 2022

Support

YARP support is provided by the product team - the engineers working on YARP - which is a combination of members from ASP.NET and the .NET library teams. We do not provide 24/7 support or 'carry pagers', but we generally have good coverage. Bugs should be reported in GitHub using the issue templates, and will typically be responded to within 24hrs. If you find a security issue we ask you to report it via the Microsoft Security Response Center (MSRC).

The support period for YARP releases is as follows:

ReleaseIssue TypeSupport period
Major or minor versionSecurity Bugs, Major behavior defectsUntil next GA + 6 Months
Patch versionMinor behavior defectsUntil next GA
PreviewSecurity Bugs, Major behavior defectsUntil next preview
All otherNone - may be addressed by next preview

For example, if 2 months after 1.3 (making up a number) is released, a security issue is found, then we will patch:

  • 1.3 - its the latest release
  • 1.2 - as it has 4 months of support remaining
  • 1.1 - provided that 1.2 was released less than 6 months before

This support schedule is designed to provide a reasonable time period for customers to be able to update to new releases.

Building your own copy of a release

YARP is an open source project, so any customers that need fixes faster, or for older releases, are able to build their own copy of YARP. The build environment for YARP is included in the repo and maintained in sync with the source. Each release (GA and Preview) of YARP is tagged, which means that if you need to patch a specific release you can sync to the tag and build. For example you can rebuild v1.0.0 with:

shell
git clone -b v1.0.0 https://github.com/dotnet/yarp.git yarp1_0_0
cd yarp1_0_0
restore.cmd 

<make your changes>

build.cmd -c release

This will produce the Yarp.ReverseProxy.dll into artifacts/bin/Yarp.ReverseProxy/Release/net6.0, and peer folder(s) for .NET 5 & Core 3.1. If you need to build a nuget package, that can be done with:

shell
pack.cmd -c release

The nuget package will be output to artifacts/packages/release/Shipping.