Skip to content

Update zio, zio-test, zio-test-sbt to 2.1.4 (#466) #598

Update zio, zio-test, zio-test-sbt to 2.1.4 (#466)

Update zio, zio-test, zio-test-sbt to 2.1.4 (#466) #598

Triggered via push June 24, 2024 11:40
Status Success
Total duration 20s
Artifacts

autoupdate.yml

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

Annotations

10 errors
autoupdate
Could not update pull request #468 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 #467 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 #463 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 #461 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 #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 #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