You ought bump this profile to when adding new LTS line. See the comment on line: 548

<jenkins.version>2.346.2</jenkins.version>

The comment outlines that .1, .3 or a later build should be used.
I'd recommend we stick to that and use .3, which I'll release tomorrow.

I think the comment is meant to just refer to the "latest" LTS build once we move the next minor LTS.

I guess timing wise that means we will always have .3 because an assumption is made on the release windows.

Thanks, guys! I will make a change after the release to use <jenkins.version>2.346.3</jenkins.version> over the next few days, most likely the day after tomorrow

I guess timing wise that means we will always have .3 because an assumption is made on the release windows.

Yeah, Tim was very early with his post this time. Timeframe wise, these kinds or PRs are typically created after the last point release took place.
Btw, doesn't updatecli take care of bumping the point release by now?

Yes @NotMyFault your absolutely right 👍 completely forgot! I even made it like that 🙄

@krisstern Lets leave the jenkins.version as it is for 2.346.x and hope the updatecli manifest generator picks up bumping jenkins.version once this is merged 👏

Sure @jetersen

@krisstern see #1390 updatecli already picked up the update 👏

Have left it draft for now, cause of @basil concerns