struklabs/harness-studio is a desktop application and local gateway for running open-source AI models such as llama.cpp directly on your own computer. The repository description states that it is a free, open-source project for running models on a personal computer. The commit 07528c5 of October 22, 2026 did not touch the application code or the model runtime, but the GitHub Actions release workflow. The commit message is "fix: share one draft across release jobs (#450)", and in the single file .github/workflows/release.yml, 42 lines were added and 2 lines were removed.
The center of the change is that one draft release per tag is shared by multiple jobs. A draft release refers to an item that is registered in the repository but has not yet been published publicly. The newly added prepare job first finds the release for that tag via the GitHub API. If none exists, it creates a draft named "Harness Studio <tag>", and if one does exist, it outputs its id. If there are two or more releases with the same tag, it does not merge them automatically but stops with an error, and it also refuses attempts to recreate an already published release. Next, the build job takes prepare as a prerequisite, the publishing stage uses the release_id handed over by prepare as is, and the organize job, which had been looking it up again by tag, was replaced by using that id. A configuration that groups the release runs for the same tag into a single group and does not cancel runs already in progress (cancel-in-progress: false) was included as well.
However, the only thing this commit touched is the deployment pipeline. The application's runtime performance, the range of compatible models, and the composition of the deployment package are not targets of this change. The published records contain no execution results or release artifacts for this fix, so whether duplicate drafts actually disappear depends on the behavior of GitHub Actions. Because draft creation comes before the build, the draft remains even if the build fails. The constraint that an already published release cannot be created again remains as it is, and if several drafts pile up, this workflow does not clean them up automatically and requires a person to merge the two.