Bump jayqi/failed-build-issue-action from 1.2.0 to 1.3.0

[dependabot]

Bumps jayqi/failed-build-issue-action from 1.2.0 to 1.3.0.

Release notes

Sourced from jayqi/failed-build-issue-action's releases.

v1.3.0

We've moved! This repository has transferred from jayqi/failed-build-issue-action to drivendataorg/failed-build-issue-action. Old references will continue to redirect but we recommend updating.

• Changed action to use Node 24 runtime.
• Changed the github-token input to default to ${{ github.token }}, the token GitHub Actions automatically provides to every job. Basic usage now needs no with: block at all. Passing github-token explicitly still works and is unchanged, and is still how you use a different account, such as a GitHub App or a personal access token.
• Renamed the refname template variable to refName, matching the camelCase of the other template variables. refname still works but is deprecated and now logs a warning when a template uses it; it will be removed in a future major version.
• Added a refUrl template variable holding a complete, percent-encoded URL to the branch or tag. The default body-template now uses it for the branch link. Prefer it over building a URL out of refName yourself: refName is display text, and for a pull request from a fork it is prefixed with the owner, e.g., contributor:feature/foo, which is not a valid URL path.
• Added label-color and label-description inputs, which set the color and description of the label when the action creates it. Both have defaults, so a newly created label gets GitHub's failing-build red and a description naming this action as its source. Both only apply to newly created labels and not to existing labels.
• Fixed refName naming the wrong branch for pull_request and workflow_run events, which had made the branch link 404 or point at the default branch rather than the branch that failed.
• Fixed refName truncating branch and tag names containing slashes, so a branch like feature/foo no longer becomes foo with a broken link.
• Fixed the default body-template hardcoding https://github.com, which generated links to the wrong host on GitHub Enterprise Server. It now uses {{serverUrl}}. Rendered output on github.com is unchanged.
• Fixed title and body templates HTML-escaping rendered values, which corrupted issue titles and code spans in issue and comment bodies.
• Fixed the search for an existing issue incorrectly matching pull requests. GitHub's REST API returns pull requests from the issues endpoint, so a pull request carrying the configured label could become the comment target and the action would never open a real issue. Pull requests are now skipped, and the action logs a warning naming any it finds with the label.
• Fixed the action making an unnecessary API request to search for existing issues when always-create-new-issue is true.
• Fixed the incorrect required: true on all inputs, changing to required: false. GitHub Actions did not enforce required for action inputs anyway, so this is a metadata fix and does not change behavior.
• Fixed debug logging of errors printing {} instead of the error. Debug output now includes the error message, stack trace, and, when the failure wraps a GitHub API error, the underlying status and response.

Changelog

Sourced from jayqi/failed-build-issue-action's changelog.

Changelog

v1.3.0 (2026-08-23)

We've moved! This repository has transferred from jayqi/failed-build-issue-action to drivendataorg/failed-build-issue-action. Old references will continue to redirect but we recommend updating.

• Changed action to use Node 24 runtime.
• Changed the github-token input to default to ${{ github.token }}, the token GitHub Actions automatically provides to every job. Basic usage now needs no with: block at all. Passing github-token explicitly still works and is unchanged, and is still how you use a different account, such as a GitHub App or a personal access token.
• Renamed the refname template variable to refName, matching the camelCase of the other template variables. refname still works but is deprecated and now logs a warning when a template uses it; it will be removed in a future major version.
• Added a refUrl template variable holding a complete, percent-encoded URL to the branch or tag. The default body-template now uses it for the branch link. Prefer it over building a URL out of refName yourself: refName is display text, and for a pull request from a fork it is prefixed with the owner, e.g., contributor:feature/foo, which is not a valid URL path.
• Added label-color and label-description inputs, which set the color and description of the label when the action creates it. Both have defaults, so a newly created label gets GitHub's failing-build red and a description naming this action as its source. Both only apply to newly created labels and not to existing labels.
• Fixed refName naming the wrong branch for pull_request and workflow_run events, which had made the branch link 404 or point at the default branch rather than the branch that failed.
• Fixed refName truncating branch and tag names containing slashes, so a branch like feature/foo no longer becomes foo with a broken link.
• Fixed the default body-template hardcoding https://github.com, which generated links to the wrong host on GitHub Enterprise Server. It now uses {{serverUrl}}. Rendered output on github.com is unchanged.
• Fixed title and body templates HTML-escaping rendered values, which corrupted issue titles and code spans in issue and comment bodies.
• Fixed the search for an existing issue incorrectly matching pull requests. GitHub's REST API returns pull requests from the issues endpoint, so a pull request carrying the configured label could become the comment target and the action would never open a real issue. Pull requests are now skipped, and the action logs a warning naming any it finds with the label.
• Fixed the action making an unnecessary API request to search for existing issues when always-create-new-issue is true.
• Fixed the incorrect required: true on all inputs, changing to required: false. GitHub Actions did not enforce required for action inputs anyway, so this is a metadata fix and does not change behavior.
• Fixed debug logging of errors printing {} instead of the error. Debug output now includes the error message, stack trace, and, when the failure wraps a GitHub API error, the underlying status and response.

v1.2.0 (2024-02-16)

• Changed action to use Node 20 runtime
• Updated dependency versions.

v1.1.1 (2023-02-11)

• Removed source map and license from build command because JasonEtco/build-and-tag-action does not support additional files.

v1.1.0 (2023-02-11)

• Added tests.
• Added more informative error if label does not exist and create-label is false.
• Updated dependency versions.

v1.0.0 (2022-07-26)

Initial release. 🚀

Commits

• 940568c Bump the dev-dependencies group across 1 directory with 2 updates (#182)
• 503f3c2 Transfer from jayqi/failed-build-issue-action to drivendataorg/failed-build-i...
• a566f41 Remove outdated development section (#181)
• bcd1cf5 feat: set label color/description on creation; document comment-target semant...
• 630f1e9 Add Zizmor audit and harden CI workflows (#180)
• 10951a0 Fix debug error logging (#179)
• 5126f13 Update integration test (#175)
• cdebeb0 Changelog maintenance
• d22929d Rename HISTORY to CHANGELOG
• fc3d425 Upgrade jest (#173)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)