JDK-26+28_adopt tag does not exist when it should

[adamfarley]

Summary

The mirror scripts won't add the JDK-26+28_adopt tag because JDK-26+28 doesn't link to our repository.

Details

We're still not building from JDK-26+28 because we have that code and the tag (so any merge doesn't change anything), but the tag doesn't point to our repository, so it isn't shown in the list of tags which are merged into our repository, which (it appears) is used to determine whether we should add a jdk-26+28_adopt tag (which we need to build temurin).

TLDR: Tag JDK-26+28 is defective, so we can't use it to make tag JDK-26+28_adopt.

This issue may just go away when the next tag drops.

Solution A

Scott will attempt to delete the jdk-26+28 tag and re-run the mirror scripts to regenerate it. - Didn't work.
Update: This only recreated the defective tag.

Solution B

Wait until JDK-26+29 drops. - Pending
This is likely to be the best solution, and since there's no JDK26 release in January, I think we can afford to wait and see if this issue resolves itself.

Solution C

Roll repo back to JDK26+ under Andrew's guidance when he returns.

[adamfarley]

This problem is not a problem, but rather intentional.

Upstream did create a tag for material which has not been merged into the master branch.

This appears to be a consequence of JDK26 being branched out of master, so our mirror scripts correctly prevented our jdk head repository from being updated with an _adopt tag when that tag (and future jdk26 tags) no longer refer to the master branch.

Closing this issue.