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

chore(deps): update react monorepo #8215

Merged
merged 2 commits into from
May 4, 2023
Merged

chore(deps): update react monorepo #8215

merged 2 commits into from
May 4, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 4, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 18.2.1 -> 18.2.2 age adoption passing confidence
@types/react-dom (source) 18.2.2 -> 18.2.3 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the release:chore This PR is a chore (means nothing for users) label May 4, 2023
@renovate renovate bot force-pushed the renovate/react-monorepo branch from a7e7abe to fd41c6f Compare May 4, 2023 01:09
@renovate renovate bot force-pushed the renovate/react-monorepo branch from fd41c6f to 713471e Compare May 4, 2023 01:13
@jtoar jtoar merged commit 1177070 into main May 4, 2023
@jtoar jtoar deleted the renovate/react-monorepo branch May 4, 2023 02:23
@redwoodjs-bot redwoodjs-bot bot added this to the next-release milestone May 4, 2023
@renovate
Copy link
Contributor Author

renovate bot commented May 4, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

jtoar pushed a commit that referenced this pull request May 4, 2023
@jtoar jtoar modified the milestones: next-release, v5.1.0 May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:chore This PR is a chore (means nothing for users)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant