{"version":"2.1.260","anchor":"self-hosted-runner-sessions-get-max-lifetime-and-termination","canonical_anchor":"self-hosted-runner-sessions-get-max-lifetime-and-termination","heading":"Self-hosted runner sessions get max-lifetime and termination hooks","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/self-hosted-runner-sessions-get-max-lifetime-and-termination","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Self-hosted runner sessions get max-lifetime and termination hooks\n\nRunner child processes gain max-lifetime and terminating lifecycle callbacks.\n\nThe self-hosted runner's child process spawn now wires up `onMaxLifetime` and `onChildTerminating` callbacks alongside the existing `onChildLifecycle`\/`onChildInit`, so the runner can react when a session hits a max lifetime limit or when a child begins terminating.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}