Skip to content

ci: name every artifact after the release file it holds - #570

Merged
OldKrab merged 1 commit into
mainfrom
shushakov/ci-artifact-names
Oct 18, 2026
Merged

OldKrab merged 1 commit into
mainfrom
shushakov/ci-artifact-names

Conversation

@OldKrab

@OldKrab OldKrab commented Oct 18, 2026

Copy link
Copy Markdown
Owner

Summary

Artifact names now follow one rule: an installable artifact is named after the release file it holds, without openaide- and the version. Failure-only uploads end in -diagnostics.

Before After File inside
vsix-<target>-g<sha> vscode-<target> openaide-vscode-<target>-VERSION.vsix
desktop-win32-x64-g<sha> desktop-windows-x64 openaide-desktop-windows-x64-VERSION.exe
desktop-darwin-arm64-g<sha> desktop-macos-arm64 openaide-desktop-macos-arm64-VERSION.dmg
android-user android openaide-android.apk (was app-release.apk)
android-debug android-debug openaide-android-debug.apk (was app-debug.apk)
android-app-server-arm64 app-server-android-arm64 openaide-app-server-android-arm64.tar.gz
app-server-<target>-g<sha> app-server-<target> bare executable used by the VSIX and Desktop builds
android-reports, android-browser-checks android-apk-diagnostics, android-browser-diagnostics test reports
  • The -g<sha> suffix and the artifact_suffix input are removed. Artifacts are scoped to their run, and the file inside already carries the version.
  • The Release workflow adds the version to the Android files, as it already does for the Linux App Server archive.

Android App Server release asset

The Termux runtime is the Android App Server, so new releases publish it as openaide-app-server-android-arm64-VERSION.tar.gz instead of openaide-termux-arm64.tar.gz, matching openaide-app-server-linux-x64-VERSION.tar.gz. The internal archive layout is unchanged.

The app reads only the release matching its own version. Apps installed from earlier releases keep reading those immutable releases, which still contain openaide-termux-arm64.tar.gz. Setup reports every lookup failure as an unavailable download, so RuntimeRelease now logs runtime_release_lookup start and end events with a fixed reason code.

Docs

The README, CODE_SIGNING.md and docs/release-policy.md still listed the Desktop files as -unsigned and -unnotarized. They now give the real names. The Android README describes the current artifacts.

Verification

  • node --test scripts/test-workspace-gate.test.mjs passes, with new assertions for the artifact and release asset names.
  • RuntimeReleaseTest and BundledRuntimeTest pass locally, including a new asset-name test.
  • actionlint reports only the two shellcheck notes already present on main.
  • npm run check:private-data passes.
  • Not yet exercised: the Build Release Artifacts and Release workflows. The next release is the first to publish the new Android asset name.

Artifact names mixed platform spellings, carried a commit suffix only
outside releases, and said nothing about the files inside them
(app-release.apk).

An installable artifact is now named after its release file, without
openaide- and the version: vscode-<target>, desktop-windows-x64,
desktop-macos-arm64, android, android-debug and app-server-android-arm64.
Failure-only uploads end in -diagnostics. The -g<sha> suffix is gone:
artifacts are scoped to their run, and the file inside already carries
the version.

The Termux runtime is the Android App Server, so it is published as
openaide-app-server-android-arm64-VERSION.tar.gz, like the Linux archive.
The app reads only the release matching its own version, so apps installed
from earlier releases keep finding openaide-termux-arm64.tar.gz there.
Setup reports every lookup failure the same way, so the lookup now logs
its outcome with a fixed reason.

The README, CODE_SIGNING.md and the release policy still listed the
Desktop files as -unsigned and -unnotarized; they now give the real names.
@OldKrab
OldKrab merged commit a409714 into main Oct 18, 2026
9 checks passed
@OldKrab
OldKrab deleted the shushakov/ci-artifact-names branch October 18, 2026 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant