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.

Sign up for GitHub

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

Jump to bottom

[BUG]: Latest release is set on v3.248.0 instead of v4.248.0 #5059

Open

4 tasks

ralucapzig opened this issue Dec 6, 2024 · 2 comments

Open

4 tasks

[BUG]: Latest release is set on v3.248.0 instead of v4.248.0 #5059

ralucapzig opened this issue Dec 6, 2024 · 2 comments

Labels

Area: Agent bug triage

ralucapzig commented Dec 6, 2024

What happened?

Steps to repro:

Invoke (https://api.github.com/repos/microsoft/azure-pipelines-agent/releases/latest
Response returns "name": "v3.248.0" > NOK, expected "v4.248.0"

Versions

n/a

Environment type (Please select at least one enviroment where you face this issue)

Self-Hosted
Microsoft Hosted
VMSS Pool
Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

No response

Version controll system

No response

Relevant log output

ralucapzig added the bug label

github-actions bot added Area: Agent triage labels

callumdaw commented Dec 9, 2024

I assume this is stopping Azure DevOps from automatically installing v4 for agent pools?

Author

ralucapzig commented Dec 9, 2024 •

edited

Loading

No, there is no negative consequence. Our agents are already updated to 4.248.0.
It's only that the version is incorrect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment