Skip to content

Use JNI cache to improve performance (#154) #49

Use JNI cache to improve performance (#154)

Use JNI cache to improve performance (#154) #49

Triggered via push October 11, 2024 14:38
Status Success
Total duration 14m 15s
Artifacts

website.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Deploy website
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected], actions/setup-java@v2, actions/cache@v2, peaceiris/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy website
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/setup-java@v2, actions/cache@v2, peaceiris/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy website
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Deploy website
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/