← All open source projects

.NET Core

dotnet/core

dotnet/core is the repository for .NET release notes, news, and lifecycle information.

Forks 4,940
Author dotnet
Language PowerShell
License MIT
Synced 2026-06-27

What It Is

dotnet/core is Microsoft’s official repository for .NET release notes, news, and discussions. It should not be confused with runtime or SDK source repositories.

Its practical value is collecting the .NET lifecycle in one place: LTS, STS, active support, maintenance, and end-of-support dates.

What Is Inside

The repository contains release notes for active and development lines. At this point, it lists .NET 11 preview, .NET 10 LTS, .NET 9 STS, and .NET 8 LTS.

Each version links to notes, patches, and announcements. For teams, it is a useful checkpoint before platform upgrades.

How People Use It

Developers and administrators use dotnet/core when planning upgrades, checking support windows, or finding the current patch level.

The repository is especially useful in corporate environments where platform version affects security, library compatibility, containers, and migration planning.

Example

The example shows the shape of an internal team note: record current line, support phase, and upgrade target.

Platform Version Note

This short record is useful next to a service upgrade plan.

Language: Markdown
## Platform

- Current: .NET 8 LTS
- Target: .NET 10 LTS
- Deadline: before end of support
- Check: release notes in dotnet/core

Strengths And Limits

dotnet/core’s strength is official lifecycle structure. It is a reliable entry point for deciding which .NET version to support next.

The limitation is that it is a reference repository, not the product codebase. Runtime or SDK source issues belong in the corresponding .NET repositories.

Project Context

.NET Core is maintained in the dotnet/core repository; its public project history starts on 2014-11-18. GitHub reports the primary language as PowerShell, and the license as MIT. The project also has a dedicated site: https://dot.net.

For a catalog page, this context matters because the reader sees a real project with an owner, license, technical base, and public change history rather than an abstract name.