v8.4.2

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Porters only:

• Removal of possibleNumberPattern in PhoneNumberMetadata.xml and ShortNumberMetadata.xml as per this announcement. These have been out of use in our library for several months. If you depend on the internal xml implementation and hadn't taken the actions detailed in the announcement, this release may break you.

Want to be notified of future releases? Join the discussion group!

v8.4.1

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes and some code changes. Upgrading to the latest release is always encouraged since phone number information changes often!

Main code changes in this release:

• isPossibleWithReason now returns the new enums INVALID_LENGTH and
  IS_POSSIBLE_LOCAL_ONLY, where these apply. We hope any users of this method have already updated their code appropriately, as per this announcement.

A reminder of example changes you might want to make, if they have not been made already:

• If you are calling isPossible, but you only want to accept possible fully-qualified numbers, you may want to switch to isPossibleWithReason and check for IS_POSSIBLE only.
• If you have a switch statement that generates messages based on the result from isPossibleWithReason you should check that these messages are appropriate for the new values as well. More details about these enums in the code, e.g. thePhoneNumberUtil javadoc

Full details in the release notes.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.4.0

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes
and some code changes. Upgrading to the latest release is always encouraged
since phone number information changes often!

New functionality in this release:

• New API methods: isPossibleNumberForType and isPossibleNumberForTypeWithReason, along with getSupportedTypesForRegion and getSupportedTypesForNonGeoEntity. These allow you to query which types (e.g. Mobile) exist for a particular region, and work out if a number is possible for that type (this is a simple length check) rather than for the region as a whole. This allows for more accurate checks than with the existing API isPossibleNumber which considered lengths of all supported types in a region (e.g. mobile, voicemail, fixed-line, etc.).

Full details in the release notes.

Note if you take advantage of this new functionality by changing your code,
it will not necessarily be trivially easy to roll back to a previous
version.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.3.3

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.3.2

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.3.1

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.3.0

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes and some code changes. Upgrading to the latest release is always encouraged since phone number information changes often!

New functionality in this release:

• Two new ValidationResult enum values have been added, which in a future release will be returned by isPossibleNumberWithReason. Please see this thread on the mailing list for a thorough explanation of changes you might need to make if you use this method.
• isNumberMatch has been improved to better compare numbers which weren't created purely by calling "parse" as recommended.
• C++ only changes: the maximum allowed length for a national significant number was increased to 17 for parity with Java, and the method ExactlySameAs to compare two phone number protos was fixed to also consider the number_of_leading_zeros field.

Full details in the release notes.

Note if you take advantage of the new enums by changing your code, it will not necessarily be trivially easy to roll back to a previous version.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.2.0

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes
and some code changes. Upgrading to the latest release is always encouraged
since phone number information changes often!

New functionality in this release:

• Made normalizeDiallableCharsOnly() API in PhoneNumberUtil (Java) public. This method is already public in the C++ implementation. It has also now been added to the Javascript implementation.

Full details in the release notes.

Note if you take advantage of this new functionality by changing your code,
it will not necessarily be trivially easy to roll back to a previous
version.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.1.0

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes and some code changes. Upgrading to the latest release is always encouraged since phone number information changes often!

New functionality in this release:

• New API in ShortNumberUtil to calculate whether a short number is carrier specific or not for a particular region (isCarrierSpecificForRegion). This API should be preferred over the old isCarrierSpecific API, which did not take region into account.

We consider a number to be carrier-specific if it connects to a different endpoint or does not connect at all, depending on the caller's carrier. With the new API a short number that is valid in multiple regions that share a country calling code (e.g. Bermuda and the United States, both of which use the country calling code 1) will now return whether it is carrier-specific or not for the particular region passed in - since it may, for example, be carrier-specific in Bermuda, but not in the United States.

Full details in the release notes.

Note if you take advantage of this new functionality by changing your code, it will not necessarily be trivially easy to roll back to a previous version.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.0.1

Greetings,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

For those who depend on libphonenumber releases from GitHub tags:
We published and deleted tags named v8.0.1 several times over 11th and 12th January while diagnosing a Maven issue that had blocked our release.

What you should do:
First, determine the impact on your project. The libphonenumber library metadata and code are identical across the different v8.0.1 publications. This probably doesn't affect you if either of the following applies:

• You didn't pick up the tag on 11th or 12th January.
• You don't copy or use the pom.xml files in any way and you don't care about the timestamp, exact size, and other build-time details of the tag's contents.

If you are affected or have any doubts, please pick up the tag that we published on 13th January, which is stable; and alert your clients and porters about any subsequent action they should take.

Please refer to the discussion group announcement for more details.

Want to be notified of future releases? Join the discussion group!