Version 1.1.0 release artifacts versions are completely off

[ava1ar]

Release version is 1.1.0, but most of artifacts attached to the release are either 1.0.1 or 1.1.1:

This makes impossible to use new version in any packaging. I am maintaining the PKGBUILD for Arch Linux in AUR and wanted to update the version, but can't right now.

[wj-xiao]

Apologies for the confusion. We are currently setting up an automated release pipeline.

Unfortunately, the v1.1.0 release was incomplete due to an incorrect version number and a missing macOS build. While I attempted to address this in v1.1.1, the automated build failed due to an issue with our Apple Developer Certificate. I have since manually built and uploaded the macOS version for v1.1.1.

All issues should now be resolved. Please use the latest build here: releases.

[hiro-gj]

Oh! 1.1.3 has the same problem, right?

#108 (comment)

[wj-xiao]

@hiro-gj Sorry, I forgot to bump the version in package.json again. Maybe I should write a script to automate this.

[ava1ar]

@wj-xiao this absolutely need to be automated. Usually the process is driven by your CI setup: you create new release in GitHub, GitHub creates new tag in git, your CI process picks the new tag, update the release version to value from tag and release new artifacts, attaching to the release in GitHub. This will make sure is it not possible to have a mismatch between versions, since it is defined only once and re-used everywhere. It totally makes sense to invest to this (or similar) setup to produce accurate releases - current releases are improssible to package for Linux distributions due to constant mismatches.

[wj-xiao]

Thanks for the suggestions. I've updated the CI, so this issue shouldn't happen again.