-
Notifications
You must be signed in to change notification settings - Fork 3.3k
ubuntu latest is set to 2404 not 2204 as per documentation #11976
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @almmechanics ,Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating. |
Can confirm. All of our pipelines using |
I also ran into this yesterday when trying to reference packages on .Net 9.0 on ubuntu-latest image. |
Hi @almmechanics - The changes will be performed by next week, we will update you accordingly. Thanks! |
Hi @almmechanics - The changes have been completed and now ubuntu 24 is ubuntu-latest. Please check from your side, closing this issue for now. Thanks! |
Description
Running
ubuntu-latest
for pipelines report back as 2404 instead of 2204 as per documentationSQL Tooling
expected forubuntu-latest
is no longer present - not previously documented as a feature of the migrationPlatforms affected
Runner images affected
Image version and build link
Current documentation indicates the Ubuntu image versions as follows
Ubuntu 22.04 ubuntu-22.04
ubuntu-latest
ORubuntu-22.04
LinkUbuntu 20.04 ubuntu-20.04
ubuntu-20.04
LinkUbuntu 24.04 ubuntu-24.04
ubuntu-24.04
LinkTaken from https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yamlUbuntu
Is it regression?
Reported in the logging as
24.04.2 LTS
Expected behavior
Latest to be in sync with the documentation
Actual behavior
Incorrect version being used
Repro steps
ubuntu-latest
as the Agent Specification (YAML or Classic have the same results)2.Create a simple task i.e. a Bash Script to run

uname -a
3. Run Pipeline and review the
Initialize Job
logged outputReports back as 24.04
The text was updated successfully, but these errors were encountered: