Release packages per OS: OS in archive names, Ubuntu 22.04/24.04/26.04

[ASDAlexander77]

What

Release packages now name the OS they were built on, and the Linux package is built for three Ubuntu releases.

Before	After (tag v0.0-pre-alpha83)
tslang-<tag>.zip	tslang-v0.0-pre-alpha83-windows-x64.zip
tslang-<tag>.tar.gz (Ubuntu 22.04)	tslang-v0.0-pre-alpha83-ubuntu-22.04-x64.tar.gz
	tslang-v0.0-pre-alpha83-ubuntu-24.04-x64.tar.gz
	tslang-v0.0-pre-alpha83-ubuntu-26.04-x64.tar.gz

How (.github/workflows/create-release.yml)

• build_on_linux runs as a matrix over ubuntu-22.04, ubuntu-24.04, ubuntu-26.04 (fail-fast: false), so each package is built, tested and packaged on the release it targets and matches that release's glibc/libstdc++.
• Linux cache keys use the Ubuntu release instead of runner.os: the cached 3rdParty folder holds a GC built on that release.
• Package install is apt-get update && apt-get install -y, so a fresh image neither lacks a package list nor stops at a prompt.
• Each Linux leg uploads its own artifact (tslang-<os>-asset); deploy_linux_asset is a matrix too and attaches one file per release.
• The Windows zip and its upload carry -windows-x64.
• tag.bat / tag_del.bat move to v0.0-pre-alpha83.

Notes

• The release workflow only runs on a tag push, so the 24.04 and 26.04 legs are first exercised by the next release; the PR test workflow deliberately stays on 22.04.
• ubuntu-26.04 is still a preview runner on GitHub.
• All three legs use the same prebuilt LLVM archive; linking it with the newer toolchains on 24.04/26.04 is expected to work but is first proven by that run.
• The existing v0.0-pre-alpha83 draft has the old file names: delete it and re-tag (tag_del.bat, then tag.bat) after this is merged.

🤖 Generated with Claude Code