Skip to content

Releases: a tag publishes the archives, dev builds as pre-releases - #66

Merged
bdbarnett merged 1 commit into
mainfrom
dev-release-path
Nov 13, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
dev-release-path

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

Pushing a version tag now builds MPVST on Windows and Linux and publishes the GitHub Release with the same archives and .sha256 sidecars the packaging scripts make by hand: the Linux tarball, the Windows zip and the Windows installer. VERSION may now hold a dev or rc version such as 0.3.5.dev0, and its tag is published as a pre-release. A final stays a signed annotated tag made by hand; the workflow takes its notes from the tag, or only uploads the archives if the release was already written.

scripts/install-release.sh [TAG] installs a released Windows build: with no tag, the newest release, pre-releases included. It checks the archive against its .sha256, stops REAPER and any engine and waits until none is running before it replaces the bundle, then compares the installed files with the archive's. --download-only stops after the checksum.

The plug-in's VST3 version and the installer's file version stay numeric (0.3.5 for 0.3.5.dev0), because hosts and Windows read them as numbers; the archive names and the installer's product version carry the full string.

Checked locally: install-release.sh --download-only against v0.3.4 (checksum OK, bundle files present), the version patterns in CMake and bash against final, dev, rc and malformed versions, and makensis building the installer with a dev version. This PR runs the release workflow without publishing, which is the first run of its Linux build; the plug-in install itself was not run here.

VERSION and the packaging scripts accept X.Y.Z.devN and X.Y.ZrcN as well
as X.Y.Z. The plug-in's VST3 version and the installer's file version
take the X.Y.Z part; the archive names and the installer's product
version carry the whole string.

release.yml builds the plug-in on Windows and Linux for a pushed version
tag, packages both with the existing scripts, and publishes the release
with every archive and its .sha256. Dev, rc, a and b tags are published as
pre-releases. A pull request that touches the release path builds and
packages without publishing.

scripts/install-release.sh downloads a release's Windows archive, checks
it against its .sha256 and installs it the way install-plugin-windows.sh
does, stopping REAPER and every engine first and refusing to go on while
any is still running. Checked: its download-only path against v0.3.4, the
version regexes in CMake and bash, and makensis with a dev version.
@bdbarnett
bdbarnett merged commit cd57ce3 into main Nov 13, 2026
6 checks passed
@bdbarnett
bdbarnett deleted the dev-release-path branch November 13, 2026 07:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant