You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
What issue are you seeing installing with this version range? We are intentionally leaving this in there for a few patch versions to allow those who were using Apollo Client with the React rc versions to continue to work. According to semver.npmjs.com this version range includes 19.0.0 as well. Any more information you can provide?
What issue are you seeing installing with this version range? We are intentionally leaving this in there for a few patch versions to allow those who were using Apollo Client with the React rc versions to continue to work. According to semver.npmjs.com this version range includes 19.0.0 as well. Any more information you can provide?
I am trying to migrate our team from React 18.3 -> 19.x.x When performing an npm install I was receiving this error.
I assumed it was because I thinking 19.0.0 < 19.0.0-rc.
After looking into this further I realize it must be because of another package (@react-google-maps/api@2.20.3) and not Apollo. I'm sorry for the inconvenience if I was incorrect.
npm error While resolving: @react-google-maps/api@2.20.3
npm error Found: react@19.0.0
npm error node_modules/react
npm error react@"19.0.0" from the root project
npm error peerOptional react@"^16.8.0 || ^17.0.0 || ^18.0.0 || >=19.0.0-rc" from @apollo/client@3.12.2. <<<<<-------
npm error node_modules/@apollo/client
npm error @apollo/client@"^3.12.2" from the root project
npm error 26 more (@react-hook/latest, ...)
npm error
Could you maybe share that package.json and lockfile so we can try that locally? According to npm's own tools, this should not result in any problems.
The problem is: if we remove the rc, we will actually break people who are still on those rcs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
removed "rc" from stable version fixing peer-deps for npm ci