SpartanJ / ecode

Lightweight multi-platform code editor designed for modern hardware with a focus on responsiveness and performance.
MIT License
933 stars 13 forks source link

FR: setup Nightly build #228

Closed ghost closed 5 days ago

ghost commented 7 months ago

Like this: https://github.com/AdeptLanguage/Adept/releases/tag/Nightly

Or this: https://github.com/pragtical/pragtical/releases/tag/rolling

Will help people that can't build their own version of ecode from latest code: https://github.com/SpartanJ/ecode/issues/227

SpartanJ commented 7 months ago

Yes, I think I'll try to setup a nightly build, also because building all the packages for a new release is currently a manual process where I depend on several computers.

Curculigo commented 3 months ago

Believe it or not, I decided to learn C++ with this very old laptop that only has 4GB of RAM. I can't afford compiling from source to access the latest fixes. A Nightly build will really help. I don't want to wait for months to get a new release!

SpartanJ commented 3 months ago

I'll try to set it up soon. I'm not very familiar with Github Actions and I was being a little lazy because of that.

SpartanJ commented 1 month ago

Nightly builds for Linux and Windows should start producing since this commit. They will be found here.

Curculigo commented 1 month ago

Can ecode nightly update itself? Or the update feature is only available on normal releases?

SpartanJ commented 1 month ago

Update notifications won't happen for the moment unless your nightly is older than a released build, nightly takes the next-release version (currently 0.6.2). It's needed a different versioning for nightly, so not for the moment.

As for self-updater is pending for all kind of releases. It's kinda tricky since there are several different distribution types (AppImage, zip/tar.gz, dmg, flatpak, and also in distro/OS repositories).

chatchoi commented 1 month ago

You can add the build number or the timestamp (or date time) to the version string.

Update: or git revision (git describe?).

SpartanJ commented 1 month ago

Yeah, git describe could come handy, but I need to change how releases are checked internally and patch the version number in code. It's not hard, but as everything, takes some time.

SpartanJ commented 1 week ago

Nightly builds started having a release number version different from the stable releases, this allows to notify if there's a new stable version newer than the nightly build you're using. I decided not to report for new nightly builds given that there's a new one every single day, I prefer to notify about stable releases.