-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beta download links #3570
Comments
The beta releases (master branch) have all the changes in the v1.49.3 branch they are just numbered incorrectly. I backported fixes from master into the v1.49.3 branch. It isn't quite as easy as you might think to change the beta base version to v1.49.3 as the v1.49.3 tag isn't on the master branch I do have a fix for this in the works though! |
Prior to this beta releases would appear to be older than the point release, eg v1.49.0-096-gc41812fc which was released after v1.49.3 and contains all the patches from v1.49.3.
You can trick travis into building off-master tags like this https://github.com/ivandeex/rclone/blob/master/.travis.yml#L7:
Github actions will need a special treatment though. |
Building them isn't the problem, it is getting the correct version back into master... I'll merge the fix for this in a moment! |
Prior to this beta releases would appear to be older than the point release, eg v1.49.0-096-gc41812fc which was released after v1.49.3 and contains all the patches from v1.49.3.
It appears the betas have changed how they are being done with numbering etc but i would still think the contains of the "beta" should have a new versions. If the latest beta is older then the last stable should it contain the stable version?
http://beta.rclone.org/rclone-beta-latest-windows-amd64.zip
contains
rclone-v1.49.0-096-gc41812fc-beta-windows-amd64
The text was updated successfully, but these errors were encountered: