Skip to content

Fix dual-read potential risk by using ThreadPool (#945) #144

Fix dual-read potential risk by using ThreadPool (#945)

Fix dual-read potential risk by using ThreadPool (#945) #144

Triggered via push November 21, 2023 01:06
Status Success
Total duration 14m 16s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

publish.yml

on: push
Matrix: publish
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
PapaCharlie
approved Nov 21, 2023
jfrog-publish

Annotations

1 warning
Java 11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/