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

Update React (major) #456

Closed
wants to merge 1 commit into from
Closed

Update React (major) #456

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 9, 2023

Mend Renovate logo banner

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-i18next 11.18.6 -> 13.3.2 age adoption passing confidence
react-native-url-polyfill 1.3.0 -> 2.0.0 age adoption passing confidence

Release Notes

i18next/react-i18next (react-i18next)

v13.3.2

Compare Source

  • types: fix consider importing '*.js'

v13.3.1

Compare Source

  • optimize defaultVariables feature introduced in last release

v13.3.0

Compare Source

  • Respect defaultVariables in the interpolation options 1685

v13.2.2

Compare Source

  • Fix missing TransWithoutContext type 1672

v13.2.1

Compare Source

  • types: Allow iterable ReactI18NextChildren as children 1669

v13.2.0

Compare Source

  • Don't use defaults prop as default key 1664

v13.1.2

Compare Source

  • postpone usage of newer ES syntax

v13.1.1

Compare Source

  • Render all children regardless of type when using i18nIsDynamicList prop 1661

v13.1.0

Compare Source

  • Fix non-list dynamic content in Trans component 1660

v13.0.3

Compare Source

  • fix unescape is not consistently called for all values 1657

v13.0.2

Compare Source

  • export icu.macro 1652

v13.0.1

Compare Source

  • types: Fix performance issue in Trans component 1646

v13.0.0

Compare Source

  • Update types to support t function redesign 1615
  • requires i18next >= v23.0.1

v12.3.1

Compare Source

  • optimization for optional lng prop for useTranslation, should now prevent missings when lazy loading translations 1637

v12.3.0

Compare Source

  • optional lng prop for useTranslation (helping on server side 1637)

v12.2.2

Compare Source

  • try to fix conditional exports in package.json

v12.2.1

Compare Source

  • type fix: the type of defaultNS in I18nextProvider should support string[] 1633

v12.2.0

Compare Source

  • if defaultValue is passed in not ready t functio (via useTranslation) return that instead of the key, even though the user-land could should be fixed 1618

v12.1.5

Compare Source

v12.1.4

Compare Source

  • fix crash in gatsby 1594

v12.1.3

Compare Source

  • fix fallback of t function in Trans component

v12.1.2

Compare Source

  • fix crash in gatsby 1594

v12.1.1

Compare Source

  • fix for node resolution 1589

v12.1.0

Compare Source

  • context-less version of Trans component to be used for environments without react context 1588

v12.0.0

Compare Source

  • Update t function types to rely on types coming from i18next 1501
charpeni/react-native-url-polyfill (react-native-url-polyfill)

v2.0.0

Compare Source

Highlights

⚠️ It was released as a major version because it contains significant changes, but we don't expect any breaking changes. The upgrade should be seamless.

Official support for Expo & web.

We're now testing react-native-url-polyfill against latest versions of Expo to prevent any issues.

Also, previously, relying on react-native-url-polyfill/auto would also apply the polyfill if executed on the web (e.g., via react-native-web). Starting from now, react-native-url-polyfill/auto won't apply on the web platform and will be a no-op. If you would like to still apply it on web, you'll need to rely on setupPolyfill directly as such:

import { setupURLPolyfill } from 'react-native-url-polyfill';

setupURLPolyfill();
Moving away from React Native's internals

To better support different versions of React Native and web usages, we moved away from using polyfillGlobal, which is part of React Native's internals. Instead, we use globalThis. See https://github.com/charpeni/react-native-url-polyfill/pull/373 and https://github.com/charpeni/react-native-url-polyfill/pull/413.

What's Changed

New Contributors

Full Changelog: charpeni/react-native-url-polyfill@v1.3.0...v2.0.0


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.

👻 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 dependencies Pull requests that update a dependency file npm labels Sep 9, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Sep 9, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN cli npm v10.2.4 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.4 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/i18next
npm ERR!   i18next@"21.10.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer i18next@">= 23.2.3" from [email protected]
npm ERR! node_modules/react-i18next
npm ERR!   react-i18next@"13.3.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/806588/1b8f24/cache/others/npm/_logs/2023-11-17T16_34_59_123Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/806588/1b8f24/cache/others/npm/_logs/2023-11-17T16_34_59_123Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react branch from 6d69449 to d92fc46 Compare September 10, 2023 06:12
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@renovate renovate bot force-pushed the renovate/major-react branch 2 times, most recently from cb85a1a to 22b96b4 Compare October 26, 2023 16:57
@renovate renovate bot force-pushed the renovate/major-react branch from 22b96b4 to d8511e4 Compare November 17, 2023 16:35
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@thornbill thornbill closed this Nov 17, 2023
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 npm
Development

Successfully merging this pull request may close these issues.

1 participant