failCmd doesn't get invoked when publishCmd returns non-zero error code

Open

#335 opened on Apr 10, 2023 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: javascript, shell
Domain: cli, release

Research direction

Reproduce the workflow using the shown publishCmd, failCmd, successCmd, and verifyConditionsCmd configuration, then inspect the semantic-release/exec handling around publishCmd errors. Compare the observed error log with the expected failure notification behavior; done means failCmd is invoked when publishCmd exits non-zero without the release crashing first.

Written by the indexing model from the issue text.

Description

semantic-release-errorlog.log
I'm trying to create a workflow where I should be able to notify on success and failure of publishCmd, but failCmd doesn't get invoked at all when publishCmd returns non-zero error code. Instead the semantic-release crashes with error stack trace.

{
  "ci": false,
  "branches": [
    "test",
    {
      "name": "beta",
      "prerelease": true
    },
    {
      "name": "alpha",
      "prerelease": true
    }
  ],
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    [
      "@semantic-release/changelog",
      {
        "changelogFile": "docs/CHANGELOG.md"
      }
    ],
    [
      "@semantic-release/exec",
      {
        "failCmd": "./fail.py",
        "successCmd": "./success.py",
        "publishCmd": "./deploy.sh \"${nextRelease.version}\"",
        "verifyConditionsCmd": "./verify.py"
      }
    ],
    [
      "@semantic-release/git",
      {
        "assets": [
          "docs/CHANGELOG.md"
        ],
        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
      }
    ]
  ]
}

Dominant language: JavaScript
Stars: 164
Forks: 28
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Resize volume API validation errors are not displayed in the UI Open

bug

Difficulty 1/5 Under an hour Newbie friendliness 90/100

apache/cloudstack#14222 · Opened Sep 22, 2026
Replay: rrweb `Mirror.removeNodeFromMap` never descends into shadow roots, so every removed web component leaks its shadow tree Open

Browser Waiting for: Product Owner

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

getsentry/sentry-javascript#24577 · 1 comment · Opened Sep 22, 2026
Write a list: documentaries that changed something Open

curation good first issue

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

amponce/archive-movie-browser#186 · Opened Sep 22, 2026
EW canvas: em+strong CTA renders green (not accent) and brochure card links misalign Open

light

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

aemdemos/patients-stryker#253 · Opened Sep 22, 2026
OAuthConsent shows an empty permissions list when only offline_access is requested Open

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

clerk/javascript#9852 · Opened Sep 22, 2026

More JavaScript issues