-
Notifications
You must be signed in to change notification settings - Fork 251
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
CI job "Release-Tarball" no longer works #352
Comments
Pull request #355 was created for this purpose. However, the question is whether the intermediate step should be taken via v3 and we then go to v4 or directly to v4. Version v4 apparently requires uniqueness in the Untested
|
I would suggest to merge PR #355 and see if it works as intended. Then we can look into using v4. Since you already started looking into it, feel free to create a pull request. |
Version 4 works |
If I understand everything correctly, the CI job already works again. We can leave this issue open until the change to version 4 is completed. |
After merging pull request #350, the automatically triggered CI job "Release-Tarball" failed with the error that it uses a deprecated API version:
The text was updated successfully, but these errors were encountered: