Skip to content

release failure issue failing to be opened #1065

@travi

Description

@travi

While working through semantic-release/npm#958, i had several situations where my configuration was not yet working, so semantic-release attempted to open the issue in the repo to report the release failure. an example failure can be found in https://github.com/travi-test/npm-oidc-test/actions/runs/16186374845/job/45692725649#step:5:106

it appears that the way we are creating the issue is failing some sort of validation of labels on the github api side. unfortunately, the error gets collapsed to prevent the error from being obvious, so i havent dug deeper to understand the issue further: https://github.com/travi-test/npm-oidc-test/actions/runs/16186374845/job/45692725649#step:5:188

the issue gets created with octokit.request and i dont see anything obvious when comparing to the rest api doc:

} = await octokit.request("POST /repos/{owner}/{repo}/issues", newIssue);

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions