You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A string representing the current Punycode.js version number.
117
117
118
+
## For maintainers
119
+
120
+
### How to publish a new release
121
+
122
+
1. On the `main` branch, bump the version number in `package.json`:
123
+
124
+
```sh
125
+
npm version patch -m 'Release v%s'
126
+
```
127
+
128
+
Instead of `patch`, use `minor` or `major` [as needed](https://semver.org/).
129
+
130
+
Note that this produces a Git commit + tag.
131
+
132
+
1. Push the release commit and tag:
133
+
134
+
```sh
135
+
git push && git push --tags
136
+
```
137
+
138
+
Our CI then automatically publishes the new release to npm, under both the [`punycode`](https://www.npmjs.com/package/punycode) and [`punycode.js`](https://www.npmjs.com/package/punycode.js) names.
139
+
118
140
## Author
119
141
120
142
| [](https://twitter.com/mathias "Follow @mathias on Twitter") |
0 commit comments