Update previous release version to 4.38 GA across build scripts

[eclipse-releng-bot]

Update the the R4_38_maintenance branch with final 4.38 release version.

This should not be submitted before 4.38 is finally released.

[HannesWell]

Looks good.

In general I think we can submit this PR a bit earlier, around the time when the final release to Maven-Central is done. Then there is no way back anyways and everything referenced here already exists then too.

I'll note that in the release notes when updating it.

[MohananRahul]

In general I think we can submit this PR a bit earlier, around the time when the final release to Maven-Central is done. Then there is no way back anyways and everything referenced here already exists then too.

I was about to say this. We’ll be able to proceed after the Maven publishing succeeds on Friday or Monday.

[merks]

What part of the processes deletes the I-builds? Because as soon as we nuke those, there will be broken builds downstream. That deletion definitely should not be happening before the release day.

We really do need to coordinate this "make visible" process with changes in the Oomph catalogs and when those are committed so that folks can smoothly transition from one working state to the next working state. Ideally I would have been able to do this step a bit earlier in the day today....

I have several states that I can commit, e.g., this "fake next release state" which I can generate by specifying the exact repository URLs in a staging mode:

eclipse-oomph/oomph@3ea6860

Once the new repositories (2026-03 including the staging 2026-03) actually exist I can generate again and all the actual children are discovered:

eclipse-oomph/oomph@7e94acb

But that step doesn't work for the Platform SDK product, because it's not visible then, so I have to leave that out of my commit.

When the downloads are visible, I can commit the final changes:

eclipse-oomph/oomph@d548092#diff-fb9f29fa0868dc51db51b209c7ab2ba46f65a91a8f3c7d067bdda43bf3864c02

And also another concern is that at least currently there are long delays between when you change something and when the server serves those changes:

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6088#note_5487973

(So even now, the generator does not see the new content just made visible. That might take another 30 minutes.)