prepare release 5.1.1 - #599
Open
alnoki wants to merge 1 commit into
Open
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.
Follow-up to #597 (Bulgaria's currency changed to EUR), which merged to
masterbut hasn't been published.This preps a patch release so the change reaches npm consumers of
world-countries:## [5.1.1] - 2026-05-29with the Bulgaria currency change (Change Bulgaria's currency to EUR #597) plus the previously-unreleased Serbian name fix (Fix Serbian 'common' and 'official' name for Hungarian #570).5.1.0→5.1.1.Patch bump since this is a data correction (Bulgaria adopted the euro on 1 Jan 2026). No
dist/index.*rebuild is needed —index.cjs/index.mjsloadcountries.jsonat runtime.Could you tag and publish
5.1.1once merged? Happy to adjust the version or changelog wording to match your preferences.