tooling moves barrier release in some cases

[dustymabe]

actually - the barrier for next got moved from 42.20250526.1.0 into the new release 42.20250609.1.0 so I'll need to fix that.

FTR this is a bug if someone would like to fix it

Originally posted by @dustymabe in #1082 (comment)

[syedahirafatima]

I would like to work on this. Could you assign me, please.

[syedahirafatima]

@dustymabe I’ve reviewed the next.json file and it looks like this issue has already been resolved. Please let me know if there’s still any work needed here, otherwise I’ll be happy to contribute to other issues in the future.

[dustymabe]

IIUC I don't think this problem is fixed. The problem is that the code that does the promotion somehow doesn't consider if there was a barrier in the one it's moving.

[marmijo]

Did the tooling move the barrier to the new release in #1082? The PR is old enough that the history isn't very clear anymore, but it looks like that rollout PR originally didn't include the barrier for next version 42.20250526.1.0 or 42.20250609.1.0 (commit). I think this happened becuase PR 1082 was opened before #1080 merged.

I ran rollout.py locally to add the new versions for this week's releases and the barriers added in #1125 were not assigned to the latest versions.

[dustymabe]

Ahh. Maybe there was some sort of race back on June 11.

If we rollout.py and don't have to fix anything for today's releases then there's no issue and can close this ticket.

[dustymabe]

Today's PR proved @marmijo right. The tooling seems to not have a bug and it was just an unfortunate timing issue in #1082 (comment)