Skip to content

Conversation

@schustmi
Copy link
Contributor

Describe changes

I implemented/fixed _ to achieve _.

Pre-requisites

Please ensure you have done the following:

  • I have read the CONTRIBUTING.md document.
  • I have added tests to cover my changes.
  • I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
  • IMPORTANT: I made sure that my changes are reflected properly in the following resources:
    • ZenML Docs
    • Dashboard: Needs to be communicated to the frontend team.
    • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
    • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (add details above)

@schustmi schustmi added the no-release-notes Release notes will NOT be attached and used publicly for this PR. label Dec 18, 2025
@github-actions github-actions bot added internal To filter out internal PRs and issues enhancement New feature or request labels Dec 18, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2026

⚠️ This PR has been inactive for 2 weeks and has been marked as stale.
Timeline:

  • Week 2 (now): First reminder - PR marked as stale
  • Week 4: PR will be automatically closed if no activity
    Please update this PR or leave a comment to keep it active. Any activity will reset the timer and remove the stale label.

@github-actions github-actions bot added the stale label Jan 2, 2026
@schustmi schustmi force-pushed the feature/improved-step-monitoring branch 3 times, most recently from 1db80b5 to 4a7a8fc Compare January 2, 2026 16:47
@github-actions github-actions bot removed the stale label Jan 3, 2026
@schustmi schustmi changed the title Improved dynamic pipeline step monitoring Improve dynamic pipeline step monitoring Jan 5, 2026
@schustmi schustmi force-pushed the feature/improved-step-monitoring branch 8 times, most recently from ad308bb to 346246a Compare January 5, 2026 14:42
@schustmi schustmi force-pushed the feature/improved-step-monitoring branch from 346246a to f49a43b Compare January 5, 2026 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request internal To filter out internal PRs and issues no-release-notes Release notes will NOT be attached and used publicly for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants