Skip to content
Fortress Security Scan

Fix #5627: SFT example notebook references inaccessible S3 dataset URI #127

Sign in to view logs

Fix #5627: SFT example notebook references inaccessible S3 dataset URI

Fix #5627: SFT example notebook references inaccessible S3 dataset URI #127

  • manual-approval requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by JiwaniZakir in Fortress Security Scan #127

Triggered via pull request March 31, 2026 01:11
@JiwaniZakirJiwaniZakir
opened #5704
Status Waiting
Total duration –
Artifacts –
  • manual-approval requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by JiwaniZakir in Fortress Security Scan #127

fortress-scan.yml

on: pull_request_target
collab-check
5s
collab-check
wait-for-approval
wait-for-approval
manual-approval waiting for review
fortress-scan
fortress-scan
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
@JiwaniZakir
JiwaniZakir
requested review
manual-approval -

Annotations

1 warning
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. Node.js 20 will be removed from the runner on September 16th, 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/