Skip to content

feat(kubeflow): add setup_commands run once per pod before the job #149

feat(kubeflow): add setup_commands run once per pod before the job

feat(kubeflow): add setup_commands run once per pod before the job #149

Triggered via pull request June 13, 2026 17:01
Status Success
Total duration 3m 10s
Artifacts 3

release.yml

on: pull_request
release  /  ...  /  check-admin-permission
4s
release / bump / check-admin-permission
release  /  ...  /  bump-next-version
7s
release / bump / bump-next-version
release  /  ...  /  build-wheel
44s
release / build-test-publish-wheel / build-wheel
release  /  ...  /  test-wheel
34s
release / build-test-publish-wheel / test-wheel
release  /  ...  /  validate-wheel
19s
release / build-test-publish-wheel / validate-wheel
release  /  ...  /  publish-wheel
6s
release / build-test-publish-wheel / publish-wheel
release  /  ...  /  notify
0s
release / build-test-publish-wheel / notify
release  /  ...  /  create-gh-release
5s
release / finalize / create-gh-release
release  /  ...  /  notify
5s
release / finalize / notify
release  /  ...  /  Build docs
32s
release / finalize / build-docs / Build docs
release  /  ...  /  publish-docs
19s
release / finalize / publish-docs
release-summary
7s
release-summary
Fit to window
Zoom out
Zoom in

Annotations

5 warnings and 4 notices
release / bump / check-admin-permission
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 16th, 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/
release / bump / bump-next-version
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-github-app-token@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
release / bump / bump-next-version
No branch protection rule found for pattern '[rv][0-9].[0-9].[0-9]'. Real releases won't be gated by a release-branch rule; skipping the admin-bypass check. Override release-branch-pattern if this repo has its own convention.
release / finalize / create-gh-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-github-app-token@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
release / finalize / publish-docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
release / build-test-publish-wheel / validate-wheel
No MANIFEST.in found; skipping check-manifest.
release / finalize / publish-docs
Publish latest: true
release / finalize / publish-docs
Commit message:
release / finalize / publish-docs
GitHub ref: refs/pull/545/merge

Artifacts

Produced during runtime
Name Size Digest
docs-html Expired
2.37 MB
sha256:cb17429a28dea68d07b5f79494baac614969b17a675296c1a72530de4228c416
linkcheck-artifact Expired
1.24 KB
sha256:ce021eaa737797f259baf9140215af5eccadfe05b16ae585b10dd361ec4cf60c
pip-wheel-27473238604-nemo_run
490 KB
sha256:2de82875329adb67ef1b3cc7289a9dcf699e1dba399c811f1033ecf719a9d3d4