Homepage and downloads · Releases · CI/CD
Community .NET SDK builds for glibc Linux AArch64 and x64, independently of Microsoft's support lifecycle. The project covers .NET 5 onward and .NET Core 3.0/3.1, using the .NET VMR where available and pinned legacy source-build graphs where needed.
Builds run exclusively in GitHub Actions. All eight selected SDK versions have passed native hosted builds and independent SDK/source delivery verification on both architectures.
Download builds or open GitHub Releases. Each version includes both SDK archives, the actual used sources for each architecture, complete qualification evidence, SHA256SUMS and release-manifest.json.
Public names use aarch64. The official .NET RID remains linux-arm64; upstream package names, container-platform identities and historical evidence retain that spelling. SDK/source payload bytes are preserved when public filenames change.
Versioned Community Build SDKs use signed project-operated APT repositories
for Ubuntu 24.04 and Debian 13 (amd64, arm64), signed RPM repositories
for Fedora 45 and Rocky Linux 9.8 (x86_64, aarch64), and Debian 13-based
GHCR SDK images (linux/amd64, linux/arm64). The
verified delivery matrix lists the exact
published SDKs and revisions. Use the
verified installation commands and
distribution status and receipts.
The Arch x86_64 recipes have passed native build, installation
and lifecycle validation; authenticated AUR submission is tracked separately in
issue #10.
The original additional SDK preparation audit
retains the source pins and dependency decisions for SDKs 9, 8, 7, 6, 5 and Core
3.1/3.0. Current availability comes from the signed publication receipts and
delivery matrix above. The cbodotnetup per-user SDK manager
provides a signed, SDK-free bootstrap for SDK10.0.403, 9.0.123, 8.0.133,
7.0.120 and 6.0.136 on the same four Ubuntu/Debian/Fedora/Rocky versions and
both native CPUs. It installs into user data roots, with explicit shell aliases
and authenticated updates/recovery. Version 0.3 adds
project SDK selection from global.json
using owned installed SDKs; explicit versions and versioned aliases take
precedence. See the 0.3.0 tool release
and activated installer status. Additional
SDK installer admissions remain separate from package qualification.
The package contract provides cbodotnet-X.Y and a common cbodotnet command
selecting the highest installed SDK series. OCI images expose
cbodotnet-X.Y, cbodotnet and dotnet for the same SDK. Public launchers show
Community Build of .NET (built by .NET Dev) in information/help; numeric
--version stdout remains compatible. CLI identity
explains the branding and source-provenance boundary.
Choose an architecture, open its workflow, and select Run workflow on main:
| Architecture | Workflow | Default native runner |
|---|---|---|
| AArch64 | Linux AArch64 SDK matrix | ubuntu-24.04-arm |
| x64 | Linux x64 SDK matrix | ubuntu-24.04 |
Alternatively, use an authenticated GitHub CLI:
gh workflow run sdk-matrix.yml --repo dotnetdev-kr/cbodotnet --ref main -f target=all -f create_draft=false
gh workflow run sdk-x64.yml --repo dotnetdev-kr/cbodotnet --ref main -f target=all -f create_draft=falseSelect all or one target:
| Target | SDK |
|---|---|
net10 |
10.0.403 |
net9 |
9.0.123 |
net8 |
8.0.133 |
net7 |
7.0.120 |
net6 |
6.0.136 |
net5 |
5.0.214 |
core31 |
3.1.426 |
core30 |
3.0.103 |
Each workflow builds at most two selected profiles concurrently. Every run uses fresh inputs and must pass its own build, upstream tests, source-delivery and native verification gates.
Actions artifacts retain run-specific transport bundles for 14 days. Public Releases preserve qualified downloads. The publication workflow promotes the exact recorded producers in the qualification catalog, independently verifies both deliveries, and publishes only a complete release. Retries accept matching assets and refuse overwrites. The Pages workflow lists complete public releases and refreshes after publication.
To resume a failed publication without rebuilding, dispatch the publication workflow with the original staged_run_id and staged_run_attempt. It requires that target's successful verification/upload job and its exact unexpired, digest-checked artifact, and retains the original publication commit.
The upstream workflow checks official stable SDK metadata every day at 03:23 UTC, including end-of-life channels. Constrained adapters cover successors to .NET 8.0.133/9.0.123 in their 1xx bands and .NET 10.0.403 in its 4xx band. Each new SDK needs both native builds, actual used sources and complete verification before automatic publication. All three generated baseline adapters have passed both native hosted builds and independent SDK/source verification and release staging.
Other bands and new major versions remain visible as pending-adapter; missing exact source tags remain pending-source, and unavailable bootstrap inputs remain pending-bootstrap. An incompatible source layout requires a qualified adapter update. Automation and recovery details describe the admission gates and retry behavior.
linux-arm64 and linux-x64 are generic glibc package targets. Native checks cover Ubuntu 22.04, Ubuntu 24.04 and Debian 13 user spaces. Kernel, system-library and optional component requirements still apply; these results do not cover musl/Alpine or every Linux distribution.
Branded .NET 5 and Core 3.x distributions use a separately authenticated OpenSSL/ICU provider; Core 3 additionally uses a separate native HTTP provider. These providers require glibc 2.34 and, on x64, x86-64-v2. Historical source-archive checks used different recorded inputs. Packaging preserves those source and framework disclosures and does not restore upstream support for EOL runtimes.
Copyright (c) 2026 cbodotnet contributors. This repository's build automation and project documentation are licensed under the MIT License, matching the upstream .NET VMR license.
SDK archives and corresponding source bundles retain their upstream copyrights, licenses and third-party notices. This repository's MIT license does not replace those terms; preserve the notices accompanying each distributed component.
- Downstream distribution contract and rollout
- CLI branding and command aliases
- Consumer SDK images and provenance
- Signed APT repositories, package coexistence and rollback
- Signed RPM repositories and qualification
- Validated Arch recipes and deferred AUR publication
- Additional SDK sources, dependency gates and preparation plans
- Current verified SDK distribution matrix
- cbodotnetup user installation, updates and recovery
- Project SDK selection and global.json limits
- Core 3 native HTTP and its separate libcurl dependency
- Downstream verification and promotion runbook
- AArch64 CI, source delivery and verification
- x64 CI, source delivery and verification
- AArch64 qualification results and artifact links
- x64 qualification results and artifact links
Documentation and code comments are maintained in English. Generated archives, downloaded inputs and build workspaces are excluded from Git.