[Question]: Is there any reason why 3.241.0 is not the latest release instead of 3.240.1?

[d-miles]

Describe your question

Hi, just curious -- 3.241.0 is not tagged as a pre-release, but is also not showing as the latest release (currently showing as 3.240.1). Is there any reason for this, or is this just a mistake? Should it not be the latest release?

I have a script that downloads the latest agent releases, but saw that our agent hasn't been updated in ~2 months so just took a quick look into why as we typically see a monthly release cycle.

Thanks!

Versions

3.241.0, 3.240.1

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

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

Azure DevOps Server (Please specify exact version in the textbox below)

Operation system

No response

Version controll system

No response

Azure DevOps Server Version (if applicable)

No response

[KonstantinTyukalov]

Hi @d-miles, with the new flow, we remove the pre-release label at the second internal stage of the version release and mark it as the latest version when it has been released to all users.
We'll update the documentation to address such updates, thanks for the heads up!

[d-miles]

Hi @KonstantinTyukalov, I guess I'm not understanding. Does that mean 3.241.0 should currently be the latest or not? Or are you saying it is not released to all users yet?

It is not marked as a pre-release, so does seem to be released to all users (unless you mean something else by this), so I'm just not sure if this is a mixup of the release labels or not.

Is there actual existing documentation that actually describes this release/pre-release labeling process, as to what you are referencing that you say needs to be updated?

[riemers]

i have 3.241.0 but latest is v3.240.1, just makes it more wilder. So i am also more confused.

[SQLSos]

Now v3.242.1 is installed when requesting an update of an agent and it is also tagged with latest. Must have happend this morning.

[SQLSos]

Now we have the same issue again. A new release comes out during the day and has no pre-release label. I also have scripts that is dependent on knowing if a new version is pre-release or latest. I don't want to trigger an update of a an agent if the version is very new. I created a separate ticket for this new release 3.243.0 #4937_

[willianantunes]

Guys, look at this issue. Same thing.