1.58.0 is missing linux-x64 and win32-arm64 builds on Open VSX #4553

On Open VSX, release 1.58.0 is published without the linux-x64 and
win32-arm64 target platforms. The same release has all seven targets on the
VS Code Marketplace.

Since the platform-specific builds are the ones that embed a JRE, a linux-x64
client falls back to the universal build, which embeds nothing. Combined with
the JDK 25 minimum introduced in 1.57.0, any Open VSX-based editor on linux-x64
without a system JDK 25+ now fails to start the language server:

Java 25 or more recent is required to run the Java extension. Please download
and install a recent JDK. You can still compile your projects with older JDKs
by configuring ['java.configuration.runtimes']

To Reproduce

1. On a linux-x64 machine with only a JDK older than 25 installed, install
   redhat.java from Open VSX (VSCodium, Theia, or any Open VSX-based editor)
   on the stable channel.
2. The gallery resolves 1.58.0 and installs the universal target, because no
   linux-x64 target is published for that version.
3. Open any Java file. The language server does not start and the Java 25
   notification appears.

Target platforms published per version, from
https://open-vsx.org/api/redhat/java/<version> compared against the
Marketplace extensionquery API:

version                  Open VSX                    MS Marketplace
-----------------------  --------------------------  --------------------------
1.55.0                   7 targets, incl linux-x64   7 targets, incl linux-x64
1.56.0                   7 targets, incl linux-x64   7 targets, incl linux-x64
1.57.0                   7 targets, incl linux-x64   7 targets, incl linux-x64
1.58.0                   5 targets, NO linux-x64     7 targets, incl linux-x64
1.58.2026101608 (pre)    7 targets, incl linux-x64   7 targets, incl linux-x64
1.59.2026102008 (pre)    7 targets, incl linux-x64   7 targets, incl linux-x64

Missing from Open VSX for 1.58.0: linux-x64 and win32-arm64.

Expected behavior

1.58.0 on Open VSX carries the same seven targets as the Marketplace, so
linux-x64 clients receive the platform build with its embedded JRE 25.

Environment

• Operating System: Amazon Linux 2023 (x86_64) under WSL2
• JDK version: Corretto 21.0.12.1 (the distro's repo snapshot carries no JDK 25)
• Visual Studio Code version: Open VSX-based editor, remote/WSL server
• Java extension version: 1.58.0, universal target, installed from Open VSX

Additional Information

The artifacts were built correctly -- the same release published all seven
targets to the Marketplace -- so this looks like the Open VSX upload of those
two not landing, rather than a packaging problem.

The publish step in .github/workflows/release.yml loops one ovsx publish
per artifact:

for platformVsix in java-*-*-${GITHUB_RUN_NUMBER}.vsix; do
  ovsx publish --skip-duplicate -p ${{ secrets.OVSX_MARKETPLACE_TOKEN }} --packagePath ${platformVsix}
done

In glob order the outcome was: darwin-arm64 ok, darwin-x64 ok,
linux-arm64 ok, linux-x64 missing, win32-arm64 missing,
win32-x64 ok. Because run: blocks execute as bash -e, a non-zero exit
would have aborted the step before win32-x64 succeeded -- so ovsx publish
appears to have exited 0 without persisting those two uploads.

Worth noting that --skip-duplicate means a re-run will not re-upload a
version Open VSX already records, so 1.58.0 probably cannot self-heal. Either a
manual upload of the two missing targets, or a republish under a new version,
would be needed.

The pre-releases immediately before (1.58.2026101608, 16-Oct) and after
(1.59.2026102008, 20-Oct) both published all seven targets from the same
workflow, which points at a single transient failure rather than a config
change.