-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
maintenance: 2405 release #2269
Conversation
* Timezone Offset Fix & Parsing with Leading Zeros * `isDate` Timezone Mock Test, Support for NodeJS <8 * `isDate` Unit Test Resiliency Improvement
* Included Regex for South African Passport Number * Corrected Passport validation * Update README.md
* Added the regex and tests for Malawi phone number validation * Added the regex and tests for Malawi phone number validation * Added the regex and tests for Malawi phone number validation
Sorry I'll delay the release to Monday. I'm also struggling having clean builds but has nothing to do with the new changes. |
@profnandaa How about we include the types in the package itself. That way it will be more easier to maintain it along with the actual lib itself. Also from the consumer point of view, this will result in one less dep, not to mention it will result in a more robust typesafety for them as we will also be changing the types file here itself instead of waiting for DefinitelyTyped |
@rubiin -- I don't mind that. Could you do a few samples to see how that will look like? |
I think most of it can be borrowed and added upon from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/validator |
@profnandaa any chance we can get this release out soon? |
@WikiRik - struggled with getting a clean build last time and stalled. I need some help on that. Was building on latest Node.js stable. |
What is the issue you got? I'm using Node 18.18.0 in a new GitHub Codespace with the default image and that works fine. You do need to use |
* chore: add additional testcases to isMailtoURI Line 44 is only partially covered before this change * chore: add additonal const to figure out which part is partial * chore: add testcase for single ? * chore: add another line to find partial coverage * chore: remove default to * chore: combine consts again
I have add LGTM labels to few issues, we can add them to this pipeline |
Co-authored-by: Musa <goat_musa@Musas-MBP.cust.communityfibre.co.uk>
@WikiRik -- this is the build errors I have been getting, I had to run with
Trying to upgrade these dev dependencies, sends everything else going crazy. Then we work on a follow up release in a month's time. Thanks for your help in reviewing the PRs and keeping the lights on! |
Currently reviewing all the LGTMs - https://github.com/validatorjs/validator.js/pulls?q=is%3Apr+is%3Aopen+label%3A%22%E2%9C%85+LGTM%22 |
* Update isPassportNumber.js Added the updated Azerbaijan passport validation: See issue: #2274 * Update validators.test.js
* Add Esperanto to alpha.js * Add Esperanto (eo) to README.md * Add tests for Esperanto validation * Fix tests * Update Esperanto tests
* Pakistan vehicles license plate support * Readme and test cases updated * Update README.md
Added isAbaRouting validator, new validator. Check whether a string is ABA routing number for US bank account & cheque ref: https://en.wikipedia.org/wiki/ABA_routing_transit_number
UPDATE: now pending this |
Co-authored-by: Rik Smale <13023439+WikiRik@users.noreply.github.com>
Lets try to include more stale prs(mc-to-land) as the number of prs are alot and the number might create a false impression for new contributors as well as users on the libs active status |
* chore: Publish to NPM with provenance The release process in this repository is already automated via GitHub Actions, which is a great first step toward creating trust in the supply chain. Recently, NPM has started to support publishing with the `--provenance` flag. This flag creates a link between the GitHub Actions run that created the release and the final artifact on NPM. This linkage further ensures that package installs can be traced back to a specific code revision. For more information on publishing with provenance, please refer to: https://github.blog/2023-04-19-introducing-npm-package-provenance/ * chore: Use Node.js 18 for publishing to support provenance
* Modified symbolRegex in isStrongPassword to include '\' * Modify test to check validity of strong password with \ character
* fix(isVAT): fixed KZ VAT number length check * fix(isVAT): fixed KZ VAT number length test
Co-authored-by: vfarylevych <vfarylevych@primocollect.com.ua>
#2391 this should fix the problem both on CI and local installs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks for the update and the merger of recent PRs!
|
This is a B release, post the main last major one #2252 , mainly to fix the regression inisDate
but escorted with a few more "feature patches".13.12.0
New Features / Validators
isAbaRouting
@songyuewFixes, New Locales and Enhancements
isLicensePlate
add Pakistanien-PK
locale @anasshakilisPort
fix invalid leading zeros @anasshakilisTaxID
added Argentinaes-AR
locale @estefrareisDate
timezone offset fix @tomaspanekisPassportNumber
addedZA
locale @GMorris-professionalisMobilePhone
:en-MW
locale @SimranSiddiquiam-AM
locale @AlexKrupkoisPostalAddress
fixNL
locale @RobinvanderVlietisISO4217
addSLE
currency @urgisStrongPassword
fix symbolRegex to include\
@nandavikasisVAT
fixedKZ
locale @MatthieuLemoineisAlpha
,isAlphanumeric
addedeo
locale @RobinvanderVlietisIBAN
add AlgeriaDZ
locale @thibault-lrisVAT
improveAU
locale @matthewberrymanisUUID
add support for v7 @rusconisTaxID
add Ukraineuk-UA
locale @arttigerisDate
disallow hiphen before year @Sumit-tech-joshi