Automated scripts will fail hard because the releases are missing.
At least the last few should be recreated.
What is with them:
https://github.com/nextcloud/contacts/releases 馃榿
Now compare with this ;) :
https://github.com/owncloud/contacts/releases
I see ... We need to build 馃懛
Maybe just upload the files from the old repo since they're already signed?
The thing I don't know is if we need a different version depending on the version of NC. If yes, then we should create at least 2 release packages, one for 9 and one for 10.
@oparoz the old releases should work for both, 9 and 10.
Any idea how we can easily copy them into this fork?
@irgendwie I would just do this then:
If the script picks up the release, then we should be good to go.
Please release 1.5.0.0 as the info.xml says that that is the version. Thanks!
@enoch85 the idea was to have the current version (working on) on the next version in the master branch. As you're using this for your scripts, I will move back to the old scheme -> updating it shortly before release/packaging.
@irgendwie Thanks!
We shouldn't need the old releases anymore.
As a side note, I'm using Github API now, and the Nextcloud scripts doesn't rely on info.xml anymore.