@romy-com/iso3166-ts 2026.9.0 → 2026.9.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +27 -5
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -5,6 +5,32 @@ no XML parsing or network access at runtime.
5
5
 
6
6
  Repository: [romy-com/iso3166-ts](https://github.com/romy-com/iso3166-ts).
7
7
 
8
+ ## Installation
9
+
10
+ **npm**
11
+
12
+ ```sh
13
+ npm install @romy-com/iso3166-ts
14
+ ```
15
+
16
+ **pnpm**
17
+
18
+ ```sh
19
+ pnpm add @romy-com/iso3166-ts
20
+ ```
21
+
22
+ **Yarn**
23
+
24
+ ```sh
25
+ yarn add @romy-com/iso3166-ts
26
+ ```
27
+
28
+ **Bun**
29
+
30
+ ```sh
31
+ bun add @romy-com/iso3166-ts
32
+ ```
33
+
8
34
  ## API
9
35
 
10
36
  ```ts
@@ -140,11 +166,7 @@ without leading zeros. For example, `2026.9.0` is the first September 2026
140
166
  release; subsequent releases that month are `2026.9.1`, `2026.9.2`, and so on.
141
167
  The first release in October becomes `2026.10.0`.
142
168
 
143
- For subsequent releases, set the version explicitly with `npm version <version>`,
144
- push the resulting commit and tag, and publish a GitHub release for that tag.
145
- The workflow installs dependencies, typechecks, tests, builds, and runs
146
- `npm publish --access public`. It does not calculate or change the version.
147
- Each npm publication requires a new version.
169
+ Bump the package version before publishing a GitHub release.
148
170
 
149
171
  ## Data provenance and licenses
150
172
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@romy-com/iso3166-ts",
3
- "version": "2026.9.0",
3
+ "version": "2026.9.2",
4
4
  "publishConfig": {
5
5
  "access": "public",
6
6
  "registry": "https://registry.npmjs.org/"