You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to try to re-run the GitHub actions or upload the Cargo.lock file manually? Edit: Just noticed that the Cargo.lock file is also in the repo, but I guess it would be nice to also have the pre-compiled binaries.
The text was updated successfully, but these errors were encountered:
The Cargo.lock file is not included in the master branch but it is
currently added for the releases (e.g. [0]). Since the GitHub deploy
action currently fails for other reasons [1] we should use the
Cargo.lock from the repository instead.
[0]: xiph/rav1e@80573d2
[1]: xiph/rav1e#2373
@lu-zero quick FYI: The
deploy / windows-binaries (gnu)
GitHub action failed for the tagv0.3.3
: https://github.com/xiph/rav1e/runs/746920332Maybe this is a transient error?:
As a result the
deploy / deploy
action wasn't run (needs windows-binaries) and the results where not added as assets to the release: https://github.com/xiph/rav1e/releases/tag/v0.3.3Would it be possible to try to re-run the GitHub actions or upload the
Cargo.lock
file manually?Edit: Just noticed that the
Cargo.lock
file is also in the repo, but I guess it would be nice to also have the pre-compiled binaries.The text was updated successfully, but these errors were encountered: