Skip to content

feature: allow kms encryped tuner output by reusing the output_data_config from the model_trainer #54

feature: allow kms encryped tuner output by reusing the output_data_config from the model_trainer

feature: allow kms encryped tuner output by reusing the output_data_config from the model_trainer #54

Triggered via pull request March 20, 2026 06:46
@MarvinBeGoodMarvinBeGood
synchronize #5630
Status Failure
Total duration 30d 0h 0m 11s
Artifacts

fortress-scan.yml

on: pull_request_target
collab-check
6s
collab-check
wait-for-approval
30d 0h
wait-for-approval
manual-approval review time expired
fortress-scan
0s
fortress-scan
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
wait-for-approval
The deployment was rejected or didn't satisfy other protection rules.
collab-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/