Skip to content

Conversation

@dependabot-preview
Copy link

Bumps icu4j from 59.1 to 66.1.

Release notes

Sourced from icu4j's releases.

ICU 66.1

Note: Please ignore the "Source code" zip & tar.gz files. (They are auto-generated by GitHub and omit the LFS file contents.)

We are pleased to announce the release of Unicode® ICU 66.

ICU 66 updates to Unicode 13, including new characters, scripts, emoji, and corresponding API constants. It also updates to CLDR 36.1 with Unicode 13 updates and bug fixes.

These new, extra Q1 releases are for integration by vendors that could not otherwise release their products with the newest version of Unicode. These are low-impact releases with no other significant feature additions or implementation changes. The next feature releases will be CLDR 37 and ICU 67, scheduled for 2020 April.

For details please see http://site.icu-project.org/download/66

The API reference documents are published at the following location: https://unicode-org.github.io/icu-docs/

*Note: The prebuilt WinARM64 binaries should be considered alpha/experimental.

ICU 66 Preview

Note: Please ignore the “Source code” zip & tar.gz files. (They are auto-generated by GitHub and omit the LFS file contents.)

ICU 66 (scheduled for 2020 March) will update to Unicode 13, and include some bug fixes. This will be a low-impact release with no other significant feature additions or implementation changes.

ICU 66 preview updates to Unicode 13 beta, including new characters, scripts, emoji, and corresponding API constants. It also updates to CLDR 36.1preview with Unicode 13 updates and bug fixes.

(The next feature release will be ICU 67, scheduled for 2020 April.)

Please test this preview release on your platforms and report bugs and regressions by using the icu-support mailing list and/or find/submit error reports.

Please do not use this preview release in production.

The preliminary API reference documents are published on https://unicode-org.github.io/icu-docs/ – follow the “Dev” links there.

*Note: The prebuilt WinARM64 binaries should be considered alpha/experimental.

ICU 66 RC

Note: Please ignore the "Source code" zip & tar.gz files. (They are auto-generated by GitHub and omit the LFS file contents.)

We are pleased to announce the release candidate for ICU 66.

ICU 66 (scheduled for 2020 March) will update to Unicode 13, including new characters, scripts, emoji, and corresponding API constants. It will also update to CLDR 36.1 with Unicode 13 updates and bug fixes.

(The next feature release will be ICU 67, scheduled for 2020 April.)

Please test this release candidate on your platforms and report bugs and regressions by using the icu-support mailing list and/or find/submit error reports.

Please do not use this release candidate in production.

The release candidate API reference documents are published on https://unicode-org.github.io/icu-docs/ – follow the “Dev” links there.

*Note: The prebuilt WinARM64 binaries should be considered alpha/experimental.

ICU 65.1

... (truncated)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [icu4j](https://github.com/unicode-org/icu) from 59.1 to 66.1.
- [Release notes](https://github.com/unicode-org/icu/releases)
- [Commits](https://github.com/unicode-org/icu/commits)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Mar 12, 2020
@dependabot-preview
Copy link
Author

Superseded by #24.

@dependabot-preview dependabot-preview bot deleted the dependabot/maven/com.ibm.icu-icu4j-66.1 branch April 23, 2020 06:44
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant