Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPM(deps): Bump react-error-boundary from 4.0.11 to 4.0.12 #898

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 18, 2024

Bumps react-error-boundary from 4.0.11 to 4.0.12.

Release notes

Sourced from react-error-boundary's releases.

4.0.12

  • Support null fallback prop (#169)
Commits
  • 54a2838 Support null fallback prop
  • 23a4d77 Fix assertion helper function
  • 8c40f40 Merge branch 'master' of github.com:bvaughn/react-error-boundary
  • 1e75248 fix(ErrorBoundary): type narrow ErrorBoundaryState (#163)
  • 04eb8af fix(useErrorBoundary): state type narrow (#161)
  • 9bbe30b 4.0.10 -> 4.0.11
  • See full diff in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

Bumps [react-error-boundary](https://github.com/bvaughn/react-error-boundary) from 4.0.11 to 4.0.12.
- [Release notes](https://github.com/bvaughn/react-error-boundary/releases)
- [Commits](bvaughn/react-error-boundary@4.0.11...4.0.12)

---
updated-dependencies:
- dependency-name: react-error-boundary
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jan 18, 2024
@dependabot dependabot bot requested review from circlecube and wpscholar January 18, 2024 15:52
Base automatically changed from develop to main January 22, 2024 23:42
@circlecube circlecube changed the base branch from main to develop January 29, 2024 22:25
@circlecube
Copy link
Member

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 30, 2024

Looks like react-error-boundary is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jan 30, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/develop/react-error-boundary-4.0.12 branch January 30, 2024 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants