Skip to content

feature: add custom entry_point support to FrameworkProcessor.run() #605

feature: add custom entry_point support to FrameworkProcessor.run()

feature: add custom entry_point support to FrameworkProcessor.run() #605

  • manual-approval requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by rauldiaz in Sagemaker PR Checks (Master) #605

Triggered via pull request April 10, 2026 14:19
@rauldiazrauldiaz
opened #5742
Status Waiting
Total duration
Artifacts
  • manual-approval requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by rauldiaz in Sagemaker PR Checks (Master) #605

pr-checks-master.yml

on: pull_request_target
collab-check
5s
collab-check
wait-for-approval
wait-for-approval
manual-approval waiting for review
detect-changes
detect-changes
Matrix: codestyle-doc-tests
Waiting for pending jobs
Matrix: integ-tests
Waiting for pending jobs
Matrix: unit-tests
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
rauldiaz
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/