Commit Graph

14 Commits

Author SHA1 Message Date
Iuri Matias 2f816a66f4 release candidate 0.7.0 RC 6 2022-10-07 14:17:50 -04:00
Iuri Matias b78a700040 release candidate 0.7.0 RC 5 2022-10-06 14:52:43 -04:00
Iuri Matias b3f063a759 release candidate 0.7.0 RC 4 2022-10-05 18:45:16 -04:00
Iuri Matias cc809a4f87 release candidate 0.7.0 RC 3 2022-10-05 14:04:49 -04:00
Iuri Matias 14523729ea release candidate 0.7.0 RC 2 2022-10-04 15:35:32 -04:00
Iuri Matias bc4ab1a34f release candidate 0.7.0 2022-09-29 11:22:11 -04:00
Iuri Matias 9f9d0a4e87 update version to 0.6.0 2022-06-30 12:11:24 -04:00
Iuri Matias a51080c17f release(@desktop): 0.5.0 beta 2022-05-17 17:13:25 -04:00
Alexandra Betouni 6852498d17 fix(desktop/version) version updated to 0.4.0
App version was still showing 0.1.0-beta.11

Closes #4116
2021-11-18 17:37:29 +02:00
Iuri Matias d7c368bcb6 bump to beta.11 2021-07-27 11:42:41 -04:00
Michael Bradley, Jr 06484ec2c0
build: bump version 2021-06-03 14:02:49 -05:00
Iuri Matias 079aa825cd update to 0.1.0-beta.9 2021-04-22 12:49:11 -04:00
Jakub Sokołowski 655097e2a2 ci: add ability to create draft GitHub releases
This adds a `Publish` stage to the combined `Jenkinsfile` which when the
`PUBLISH` parameters is true pushes a __draft__ release to GitHub.
The job remembers the last value of `PUBLISH` parameter selected.

The release uses the contents of the `VERSION` file at the root of the
repo as the name for the release, and leaves the contents to be filled
in by whoever will approve the release.

The automation overwrites - or to be exact, deletes and recreates - the
release, so releated builds for the same release will simply re-create
it. All the built artifacts are included in the release.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2021-04-20 12:53:43 -04:00
Iuri Matias f4062abc6b add version file 2021-04-16 08:40:49 -04:00