Skip to content

build(deps-dev): bump react-error-boundary from 5.0.0 to 6.1.1 - #4495

Open
dependabot[bot] wants to merge 4 commits into
masterfrom
dependabot/npm_and_yarn/react-error-boundary-6.1.1
Open

build(deps-dev): bump react-error-boundary from 5.0.0 to 6.1.1#4495
dependabot[bot] wants to merge 4 commits into
masterfrom
dependabot/npm_and_yarn/react-error-boundary-6.1.1

fix security findings

5f2f67d
Select commit
Loading
Failed to load commit list.
DCO-2 / DCO required action Jun 25, 2026 in 0s

Check failed

There is one commit incorrectly signed off, the check did not pass.

Summary


Sha Message Pass or fail reason
🟢 d9c3977 build(deps-dev): bump react-error-boundary from 5.... Skipped: sign-off not required in bot commit
🟢 e9f2242 Apply make generate changes Skipped: sign-off not required in bot commit
🟢 6f1d7f1 Merge branch 'master' of github.com:target/goalert... Skipped: sign-off not required in merge commit
🔴 5f2f67d fix security findings Sign-off not found

Errors details

Sign-off not found

No sign-off was found in the commit message. This usually means that the author or committer of this commit failed to include a Signed-off-by line in the commit message. In some cases, this error can also be raised if the sign-off is not in the correct format.

To avoid having pull requests blocked in the future, always include a Signed-off-by: User1 <user1@email.test> line in every commit message. You can also do this automatically by using the -s flag (i.e., git commit -s).

How to fix missing or invalid sign-offs

Option 1: add remediation commit

Option 2: fix commits without sign-off

Amend last commit

To fix the incorrectly signed off commit:

  1. Ensure you have a local copy of your branch by checking out the pull request locally via command line.
  2. In your local branch, run: git commit --amend --signoff
  3. Force push your changes to overwrite the branch: git push --force-with-lease origin dependabot/npm_and_yarn/react-error-boundary-6.1.1