Skip to content

Update zio, zio-test, zio-test-sbt to 2.1.10 (#501) #616

Update zio, zio-test, zio-test-sbt to 2.1.10 (#501)

Update zio, zio-test, zio-test-sbt to 2.1.10 (#501) #616

Triggered via push October 10, 2024 13:53
Status Success
Total duration 25s
Artifacts

autoupdate.yml

on: push
autoupdate
16s
autoupdate
Fit to window
Zoom out
Zoom in

Annotations

10 errors
autoupdate
Could not update pull request #500 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #494 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #497 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #496 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #495 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #492 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #395 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #490 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #484 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #483 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration