Skip to content

Bump vite from 4.5.10 to 4.5.11 in /applications/feedback_sentiment_a… #4

Bump vite from 4.5.10 to 4.5.11 in /applications/feedback_sentiment_a…

Bump vite from 4.5.10 to 4.5.11 in /applications/feedback_sentiment_a… #4

Triggered via push April 1, 2025 16:57
Status Success
Total duration 29s
Artifacts
Auto Update PR
19s
Auto Update PR
Fit to window
Zoom out
Zoom in

Annotations

7 errors
Auto Update PR
Could not update pull request #7327 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
Auto Update PR
Could not update pull request #7321 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
Auto Update PR
Could not update pull request #7331 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
Auto Update PR
Could not update pull request #7336 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
Auto Update PR
Could not update pull request #7326 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
Auto Update PR
Could not update pull request #7314 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
Auto Update PR
Could not update pull request #7305 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