Repository navigation
Conversation
A commit message such as "closes semantic-release#123" copied from another repository made the getRelatedIssues GraphQL query return a NOT_FOUND error, which octokit throws even though the response carries partial data. That failed the whole success step. Treat NOT_FOUND-only errors as missing issues, log them, and continue with the ones that resolved. Any other error is still thrown. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🎉 This PR is included in version 12.0.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
If a commit message references an issue number that doesn't exist in the repository (e.g.
closes #3068copied from another repo, which is common in forks and monorepo migrations), thegetRelatedIssuesGraphQL query returns partialdataplus aNOT_FOUNDerror.@octokit/graphqlthrows on anyerrors, so the wholesuccessstep fails:This is inconsistent with the existing handling of missing issues when commenting (404 is logged and ignored, see "Ignore missing and forbidden issues/PRs").
Change
NOT_FOUNDand partial data is present, log the missing numbers and continue with the issues that resolved (null entries are filtered out).npm run lint:prettierandava(266 tests) pass.