forked from google/libphonenumber
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] master from google:master #3
Open
pull
wants to merge
130
commits into
makesoftwaresafe:master
Choose a base branch
from
google:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
* [maven-release-plugin] prepare release v8.13.28 * [maven-release-plugin] prepare for next development iteration
* Update lock_posix.h Remove uses of the deprecated DISALLOW_COPY_AND_ASSIGN in favor of explicitly deleted constructors and assignment operators. * Remove uses of the deprecated DISALLOW_COPY_AND_ASSIGN in favor of explicitly deleted constructors and assignment operators.
* [maven-release-plugin] prepare release v8.13.29 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.30 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.31 * [maven-release-plugin] prepare for next development iteration
* Update java runtime version to support App Engine * Adding version number for maven-compiler * Update maven-compiler configuration * Update pom.xml * Update App engine properties * Update pom.xml
* [maven-release-plugin] prepare release v8.13.31 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.32 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.33 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.34 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.35 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.51 * [maven-release-plugin] prepare for next development iteration
* Update osv-scanner-unified.yml * Update osv-scanner-unified.yml Updating version
Signed-off-by: Joyce <[email protected]> Co-authored-by: Tijana Vislavski Gradina <[email protected]>
* Added Automatic-Module-Name to published jars. Context: https://b.corp.google.com/issues/308334884 * Removed Automatic-Module-Name from carrier and geocoder. Classes in these modules belong to the same package as core libphonenumber library, which leads to the split package problem with Java modules.
* [maven-release-plugin] prepare release v8.13.52 * [maven-release-plugin] prepare for next development iteration
* Fix regex logic * Simplify code * Fix variable name * Add case insensitive option for regexp
* Strip extension before appending formatted extension. * Add pending code change --------- Co-authored-by: Tijana Vislavski Gradina <[email protected]>
#3771) * Added Automatic-Module-Name to published jars. Context: https://b.corp.google.com/issues/308334884 * Removed Automatic-Module-Name from carrier and geocoder. Classes in these modules belong to the same package as core libphonenumber library, which leads to the split package problem with Java modules. * Documented the issue with checking isPossible only for default country
* [maven-release-plugin] prepare release v8.13.53 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release v8.13.54 * [maven-release-plugin] prepare for next development iteration
To fix the osv-scanner workflow failure
* [maven-release-plugin] prepare release v8.13.55 * [maven-release-plugin] prepare for next development iteration
#3816) * Increse the java version from 7 to 8 to compatible pom's
* [maven-release-plugin] prepare release v9.0.0 * [maven-release-plugin] prepare for next development iteration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )