[builds-builder,dotnet] migrate to Heroku buildpack for dotnet 10
Open, MediumPublicFeature
Actions

Assigned To

None

Authored By

	Hawkeye7
	Dec 15 2025, 2:44 AM

Description

Feature summary :

Microdosft released .NET 10 on 11 November 2025. [https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core] With .NET 10 now available, the clock is ticking on previous versions. Both .NET 8 and .NET 9 will reach End of Support on 10 November 2026. In other words, now is a good time to start planning a migration. Heroku has support for .NET 10. [https://www.heroku.com/blog/support-for-dotnet-10-lts-what-developers-need-know/]

Can we get the toolforge to handle .NET 10?

Benefits : This will ensure .NET availability until November 2028

Event Timeline

Hawkeye7 created this task.Dec 15 2025, 2:44 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 15 2025, 2:44 AM

Pppery edited projects, added Toolforge; removed Toolforge Build Service.Dec 15 2025, 2:56 AM

Restricted Application added a project: cloud-services-team. · View Herald TranscriptDec 15 2025, 2:56 AM

Hawkeye7 updated the task description. (Show Details)Dec 15 2025, 8:50 PM

fgiunchedi triaged this task as Medium priority.Dec 19 2025, 1:25 PM

I couldn't get heroku:24 to work, but I was able to build .NET 10 with

pack build $CONTAINER --buildpack paketo-buildpacks/dotnet-core --builder docker.io/paketobuildpacks/ubuntu-noble-builder-buildpackless  --env BP_DOTNET_PROJECT_PATH=./$TARGET

where $CONTAINER is the name of my container and $TARGET the directory it is in

[builds-builder,dotnet] migrate to Heroku buildpack for dotnet 10Open, MediumPublicFeatureActions

Description

Event Timeline

[builds-builder,dotnet] migrate to Heroku buildpack for dotnet 10
Open, MediumPublicFeature
Actions