Skip to content

Update zio, zio-test, zio-test-sbt to 2.1.12 (#513) #622

Update zio, zio-test, zio-test-sbt to 2.1.12 (#513)

Update zio, zio-test, zio-test-sbt to 2.1.12 (#513) #622

Triggered via push November 9, 2024 14:38
Status Success
Total duration 29s
Artifacts

autoupdate.yml

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

Annotations

10 errors
autoupdate
Could not update pull request #512 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 #511 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 #505 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 #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 #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 #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