Fix for softlocks when initializing/exiting the application and minor issues with backup/restore #474
Annotations
8 errors and 2 warnings
Post Docker Layer Caching
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Post Docker Layer Caching
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Post Docker Layer Caching
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Post Docker Layer Caching
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Post Docker Layer Caching
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Post Docker Layer Caching
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Post Docker Layer Caching
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Post Docker Layer Caching
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "SaveMiiModWUTPort-Aroma", "SaveMiiModWUTPort-HBL".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, jpribyl/[email protected], actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Loading