Skip to content

feat: support for ForceFlush of LoggerProvider and unified naming #394

feat: support for ForceFlush of LoggerProvider and unified naming

feat: support for ForceFlush of LoggerProvider and unified naming #394

Triggered via pull request September 13, 2024 09:44
Status Success
Total duration 1m 26s
Artifacts

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (1.22.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (1.22.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (1.21.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (1.21.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/