feat: deprecate GTS image tag and migrate to stable

[ahmedadan]

This removes the dedicated GTS build pipeline and instead adds gts as a tag alias produced by the stable build, done in two parts within the same PR:

1. Repoints gts → stable: On weekly Tuesday builds and workflow_dispatch, the stable build now produces versioned gts tags (gts-${version}, gts-${version:3}) alongside the existing stable tags.
2. Removes GTS CI: Deletes the dedicated build workflow, strips gts from the Justfile, release generation, and all docs/comments.

[castrojo]

End of an era! <3

[castrojo]

In my review the agent noticed a missing gts floating tag for the undated versions and is recommending this:

In Justfile, all three production stable branches need "gts" added:

•    BUILD_TAGS+=("stable" "stable-${version}" "stable-${version:3}" "gts-${version}" "gts-${version:3}")
  

•    BUILD_TAGS+=("stable" "stable-${version}" "stable-${version:3}" "gts" "gts-${version}" "gts-${version:3}")
  

That's three identical lines (schedule, workflow_dispatch/call, local build) — same single token added to each. No other files need changing.

[castrojo]

Ok I'm heading on a trip for the next week so if we're good with this then let's get it ready to deploy? Is there a way to test this ahead of time?

[renner0e]

Ok I'm heading on a trip for the next week so if we're good with this then let's get it ready to deploy? Is there a way to test this ahead of time?

Testing it in a fork and seeing if it actually pushes the same GTS tags on the stable workflows?

[castrojo]

Tested in a branch ... here's the run logs for each image, manual review strongly preferred. 😄

• Workflow run: https://github.com/castrojo/bluefin/actions/runs/22684304133
• Job — image (main, bluefin, stable): https://github.com/castrojo/bluefin/actions/runs/22684304133/job/65762980612
• Job — image (main, bluefin-dx, stable): https://github.com/castrojo/bluefin/actions/runs/22684304133/job/65762980566
• Job — image (nvidia-open, bluefin, stable): https://github.com/castrojo/bluefin/actions/runs/22684304133/job/65762980555
• Job — image (nvidia-open, bluefin-dx, stable): https://github.com/castrojo/bluefin/actions/runs/22684304133/job/65762980629
• Registry — bluefin: https://github.com/castrojo/bluefin/pkgs/container/bluefin
• Registry — bluefin-dx: https://github.com/castrojo/bluefin/pkgs/container/bluefin-dx
• Registry — bluefin-nvidia-open: https://github.com/castrojo/bluefin/pkgs/container/bluefin-nvidia-open
• Registry — bluefin-dx-nvidia-open: https://github.com/castrojo/bluefin/pkgs/container/bluefin-dx-nvidia-open

[hanthor]

Ok I'm heading on a trip for the next week so if we're good with this then let's get it ready to deploy? Is there a way to test this ahead of time?

Testing it in a fork and seeing if it actually pushes the same GTS tags on the stable workflows?

@ahmedadan I'm not seeing the part where gts is getting pointed to stable can you point it out?

[ahmedadan]

@hanthor It's listed here, you can see the tags applied in @castrojo fork: https://github.com/castrojo/bluefin/pkgs/container/bluefin-nvidia-open/717881883?tag=gts-43.20260304

[ahmedadan]

More specifically it's in the generate tag and tags images and step in reusable-build.yml, https://github.com/castrojo/bluefin/actions/runs/22684304133/job/65762980566#step:15:23

[castrojo]

@bsherman @bketelsen @KyleGospo @tulilirockz @hanthor @ahmedadan @daegalus @marcoceppi @p5 and everyone else who helped shape Bluefin. Please feel free to leave some words for our now extinct Bluefin GTS.

Someday I will make a GNOME -1 branch in Dakotaraptor out of sheer hatred for extension jank.

Goodbye Bluefin GTS, you were the first of her kind, the holotype.