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

fix(deps): update react monorepo to v19 (major) #1855

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 5, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 18.3.17 -> 19.0.1 age adoption passing confidence
@types/react-dom (source) 18.3.5 -> 19.0.2 age adoption passing confidence
react (source) 18.3.1 -> 19.0.0 age adoption passing confidence
react (source) ^18.2.0 -> ^18.2.0 || ^19.0.0 age adoption passing confidence
react-dom (source) 18.3.1 -> 19.0.0 age adoption passing confidence
react-dom (source) ^18.2.0 -> ^18.2.0 || ^19.0.0 age adoption passing confidence

Release Notes

facebook/react (react)

v19.0.0

Compare Source

facebook/react (react-dom)

v19.0.0

Compare Source


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Dec 5, 2024
Copy link

changeset-bot bot commented Dec 5, 2024

🦋 Changeset detected

Latest commit: 8b719c9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@theguild/components Patch
@theguild/editor Patch
@theguild/remark-mermaid Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

github-actions bot commented Dec 5, 2024

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
@theguild/components 7.3.3-alpha-20241205185452-12f84d707024635ee7af19a4c66f73bbf7164adf npm ↗︎ unpkg ↗︎
@theguild/editor 1.3.11-alpha-20241205185452-12f84d707024635ee7af19a4c66f73bbf7164adf npm ↗︎ unpkg ↗︎
@theguild/remark-mermaid 0.1.4-alpha-20241205185452-12f84d707024635ee7af19a4c66f73bbf7164adf npm ↗︎ unpkg ↗︎

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 12f84d7 to 980fc29 Compare December 9, 2024 15:30
@renovate renovate bot changed the title fix(deps): update react monorepo to v19 (major) chore(deps): update react monorepo to v19 (major) Dec 9, 2024
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 5449b6b to 3dcfc30 Compare December 9, 2024 15:49
@dimaMachina dimaMachina force-pushed the renovate/major-react-monorepo branch from cee0ac0 to e9dd229 Compare December 9, 2024 15:58
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 2820f49 to 01cdcc7 Compare December 17, 2024 06:01
@renovate renovate bot changed the title chore(deps): update react monorepo to v19 (major) fix(deps): update react monorepo to v19 (major) Dec 17, 2024
Copy link
Contributor Author

renovate bot commented Dec 17, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants