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 dependency cldr-localenames-modern to v45 #220

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cldr-localenames-modern (source) 38.1.0 -> 45.0.0 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

unicode-cldr/cldr-json (cldr-localenames-modern)

v45.0.0: CLDR 45 Final Data

Compare Source

What's Changed

New Contributors

Full Changelog: unicode-org/cldr-json@44.1.0...45.0.0

v44.1.0

Compare Source

Full Changelog: unicode-org/cldr-json@44.0.1...44.1.0

v44.0.1

Compare Source

44.0.1 is the same as 44.0.0 except for the version number, for compatibility with NPM, for which there was a problem with 44.0.0 being created prematurely.

One other difference is that the zip files for 44.0.0 included ".DS_Store", a harmless file used on macOS.

v44.0.0

Compare Source

44.0.0

v43.1.0

Compare Source

See https://cldr.unicode.org/index/downloads/cldr-43 for more about CLDR 43.1

the npm packages will be tagged @latest and also @43.1.0 ( so [email protected] etc)

See package list: https://github.com/unicode-org/cldr-json/blob/43.1.0/PACKAGES.md
What's Changed

Full Changelog: unicode-org/cldr-json@43.0.0...43.1.0

v43.0.0: - CLDR v43

Compare Source

See https://cldr.unicode.org/index/downloads/cldr-43 for more about CLDR 43

the npm packages will be tagged @latest and also @43.0.0 ( so [email protected] etc)

See package list: https://github.com/unicode-org/cldr-json/blob/43.0.0/PACKAGES.md
What's Changed
New Contributors

Full Changelog: unicode-org/cldr-json@42.0.0...43.0.0

v42.0.0: CLDR 42.0.0 final

Compare Source

See https://cldr.unicode.org/index/downloads/cldr-42 for more about CLDR 42

the npm packages will be tagged @latest and also @42.0.0 ( so [email protected] etc)

See package list: https://github.com/unicode-org/cldr-json/blob/42.0.0/PACKAGES.md

v41.0.0: - cldr-json for release-41

Compare Source

CLDR-15402 v41 CLDR-JSON generate from release-41

See https://cldr.unicode.org/index/downloads/cldr-41 for general CLDR info.

  • Package list: PACKAGES

  • For npm you can use for example [email protected]

  • Note: only version number change since beta2.

  • cldr-json info

  • DATA: unicode-org/cldr-staging: 36caa1c release-41
  • TOOL: unicode-org/cldr: 1e28c0f release-41
  • SCRIPT: unicode-org/cldr-json: 2a6df0c 41.0.0-BETA2-1-g2a6df0c0d

v40.0.0: - CLDR v40

Compare Source

CLDR 40

📝 Note: as of 2022-02-14 the zipfiles have been rereleased to correct for CLDR-15158

👉 See https://cldr.unicode.org/index/downloads/cldr-40 for details about CLDR 40

👉 👉 Especially see https://cldr.unicode.org/index/downloads/cldr-40#h.nssoo2lq3cba with JSON data changes. 👈 👈

For the (new!) list of packages, see https://github.com/unicode-org/cldr-json/blob/40.0.0/PACKAGES.md#cldr-json-packages

PRs here

New Contributors

Full Changelog: unicode-org/cldr-json@39.0.0...40.0.0

v39.0.0

Compare Source

Release of CLDR v39 for JSON. Available here or on npm under the tag 39.0.0

For more information about cldr-json, see https://github.com/unicode-org/cldr-json

Please note the following upcoming changes, planned for CLDR v40

  • CLDR-14642 : The en-US-POSIX locale will be affected in some way, and also root will be renamed to und. This will leave cldr-json with only bcp47 compliant data files. Please keep an eye on this issue for further changes.
  • CLDR-14571 : This is a proposal to add bcp47 data into the cldr-json files. See this issue for more details.

Configuration

📅 Schedule: Branch creation - "after 5pm on the 2nd day of the month" (UTC), 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 this update again.


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

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

Copy link
Contributor Author

renovate bot commented Nov 2, 2024

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: sponge-docs-theme@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/cldr-core
npm ERR!   dev cldr-core@"38.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer cldr-core@"45.0.0" from [email protected]
npm ERR! node_modules/cldr-localenames-modern
npm ERR!   dev cldr-localenames-modern@"45.0.0" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-02T20_01_28_896Z-debug-0.log

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