Skip to content

runtime: treat a thrown job error as a crash, not a recoverable fail - #1552

Closed
doc-han wants to merge 1 commit into
mainfrom
demo-joberror-severity-break
Closed

doc-han wants to merge 1 commit into
mainfrom
demo-joberror-severity-break

Conversation

@doc-han

@doc-han doc-han commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

An error thrown from user job code shouldn't let the workflow limp on to downstream steps with no output to work from - abort the run instead.

Short Description

A one or two-sentence description of what this PR does.

Fixes #

Implementation Details

A more detailed breakdown of the changes, including motivations (if not provided in the issue).

QA Notes

List any considerations/cases/advice for testing/QA here.

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

  • I have used Claude Code
  • I have used another model
  • I have not used AI

You can read more details in our
Responsible AI Policy

Release branch checklist

Delete this section if this is not a release PR.

If this IS a release branch:

  • Run pnpm changeset version from root to bump versions
  • Run pnpm install
  • Commit the new version numbers
  • Run pnpm changeset tag to generate tags
  • Push tags git push --tags

Tags may need updating if commits come in after the tags are first generated.

An error thrown from user job code shouldn't let the workflow limp on to
downstream steps with no output to work from - abort the run instead.
@github-project-automation github-project-automation Bot moved this to New Issues in Core Sep 17, 2026
@doc-han doc-han closed this Sep 17, 2026
@github-project-automation github-project-automation Bot moved this from New Issues to Done in Core Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants