Skip to content

Update zio, zio-test, zio-test-sbt to 2.1.1 (#456) #591

Update zio, zio-test, zio-test-sbt to 2.1.1 (#456)

Update zio, zio-test, zio-test-sbt to 2.1.1 (#456) #591

Triggered via push May 11, 2024 13:21
Status Success
Total duration 25s
Artifacts

autoupdate.yml

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

Annotations

10 errors
autoupdate
Could not update pull request #454 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 #444 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 #452 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 #451 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 #450 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 #449 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 #448 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 #437 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 #426 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