-
Notifications
You must be signed in to change notification settings - Fork 37
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
Support New Benin Phone Number Format (Forced Effective November 30, 2024) #77
Comments
It appears that the changes to support Benin's updated phone number format (effective October 31, 2024) have already been implemented in the metadata. Specifically: The "01" prefix for 10-digit numbers is present in the patterns. Parsing: The library fails to correctly identify or parse some valid 10-digit numbers with the "01" prefix. |
ah, i see in commit 9bb32eb that the changes were made yesterday. When will this be released? |
This repo would really benefit from an auto publish action, but I've no time to add that yet. Will release now. |
Happy to do the work for it if you wanted to assign me the ticket? |
There is this issue #73 . Do you want / need write access ? |
yeah for the ENV |
I do not think you need write access for this (but I sent you an invite anyway). I added the following configuration to the package on pub.dev here is publish.yml example name: Publish to pub.dev
on:
push:
tags:
- 'v[0-9]+.[0-9]+.[0-9]+*'
jobs:
publish:
permissions:
id-token: write # Required for authentication using OIDC
uses: dart-lang/setup-dart/.github/workflows/publish.yml@v1
# with:
# working-directory: path/to/package/within/repository |
Cool thanks ill get on it soon |
Support New Benin Phone Number Format (Effective November 30, 2024)
Description
Benin updated its phone number format on November 30, 2024, to accommodate the increasing number of users. The change includes the addition of the "01" prefix to all existing numbers, extending the total length to 10 digits.
New Format Details:
Key Requirements:
References:
The text was updated successfully, but these errors were encountered: