Skip to content

Restore updater-compatible Vivaldi release filenames - #101

Merged
czyt merged 1 commit into
mainfrom
codex/restore-release-asset-names
Nov 16, 2026
Merged

czyt merged 1 commit into
mainfrom
codex/restore-release-asset-names

Conversation

@czyt

@czyt czyt commented Nov 16, 2026

Copy link
Copy Markdown
Member

Existing Vivaldi update services depend on windows_x64.zip, windows_x86.zip and windows_arm64.zip. Restore those public filenames; keep Chrome's chrome-windows-*.zip names unchanged and keep version.dll at the root of each archive.

Add a pre-publish contract guard and a Linux smoke test that executes the actual workflow packaging scripts. It checks all six names, the architecture-specific DLL payload, and rejection of renamed assets or missing DLLs. Update the documentation and patch version to 1.6.2.1.

Validation: https://github.com/ca-x/vivaldi_plus/actions/runs/43791969807

The existing v1.6.1.0 and v1.6.2.0 Vivaldi asset metadata has already been repaired without changing asset IDs, binary payloads or Chrome assets.

Restore windows_x64.zip, windows_x86.zip and windows_arm64.zip for Vivaldi while retaining Chrome's current archive names. Verify the actual packaging scripts and payloads on Linux, and reject missing or renamed updater assets before publishing.

Constraint: Release asset names are consumed as a stable external update API

Confidence: high

Scope-risk: narrow

Tested: Existing releases repaired through asset metadata with unchanged file sizes; script syntax and diff checks

Not-tested: Linux packaging smoke test and three-architecture builds await Actions
@czyt
czyt merged commit 328c978 into main Nov 16, 2026
5 checks passed
@czyt
czyt deleted the codex/restore-release-asset-names branch November 16, 2026 02:34
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