Skip to content

fix: memory leak on Windows when calling SwapMemory (#72) #332

fix: memory leak on Windows when calling SwapMemory (#72)

fix: memory leak on Windows when calling SwapMemory (#72) #332

Triggered via push October 5, 2024 10:52
Status Success
Total duration 1m 19s
Artifacts
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Analyze (javascript)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4, github/codeql-action/init@v2, github/codeql-action/autobuild@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Analyze (javascript)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Analyze (go)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4, github/codeql-action/init@v2, github/codeql-action/autobuild@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Analyze (go)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/