Version Packages - #23
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
naija-id@0.5.3
Patch Changes
d7f1b1d: Trim
keywordsfrom 37 to 10, reversing the previous expansion.The expansion in 0.5.2 pushed in the wrong direction. Measuring the "nuban" result set (n=14 packages that all carry the term in their description), search score correlates negatively with keyword count (−0.24), description length (−0.30) and how late the term appears in the description (−0.29) — the signature of TF-IDF field-length normalisation. Every extra keyword dilutes the ones that matter. For scale,
#1 nubancarries 2 keywords and a 47-character description; we carried 37 and 186.The expansion caused no measured harm (
nubanwas feat: generator parity — every identifier gets a generate* counterpart #8 before and feat: generator parity — every identifier gets a generate* counterpart #8 after), so this is a course correction rather than a bug fix.Kept, because these are the terms that measurably rank:
vninrsa-pinbvnnaijanubannincactinPlus
tax-id(the current NRS identifier — high intent, no ranking data yet) andnigeria(the country term, and it appears in the multi-word queries).Dropped 27, all of which returned no ranking at all when tested directly:
kyc,pii,redaction,identity,e164,msisdn,phone,plate,passport,validation,validatorand the spelled-out variants added in 0.5.2. These sit in crowded generic fields where npm's name-token matching decides the result, so they contributed dilution and nothing else.The description is deliberately unchanged. Front-loading identifier names would improve term position, but it is the human-facing line on the npm page and in GitHub search results — trading readability for a couple of positions on a query where the exact-name package outscores us 13× is a bad deal.