Bad signer as 2025-09 release cycle completes

[ewillink]

I wrote on simrel-dev

Ed Merks responded with a probable diagnosis:

[merks]

It turns out @ewillink is actually using 4.38 which does have a new signing problem.

The published Maven artifacts are fine!

[ewillink]

It turns out @ewillink is actually using 4.38 which does have a new signing problem.

Yes and No. Using https://download.eclipse.org/eclipse/updates/I-builds which had just flipped up to 4.38.

Good to see that the split-package signer hazard is now diagnosed by a test.
Can we please ensure that developers are aware of the failure and that promotion to I-builds does not occur.

[merks]

The test runs on the promoted build and runs on oomph’s ci instance. Maybe someone else wants to improve that.

[merks]

The composite switched to 4.38 on 2025-08-29.

I've verified that the latest 4.38-I-build fixes the problem: