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
Copy file name to clipboardExpand all lines: README.md
-22Lines changed: 0 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,28 +44,6 @@ var endsWith = require('string.prototype.endswith');
44
44
45
45
Polyfills + test suites for [`String.prototype.startsWith`](https://mths.be/startswith) and [`String.prototype.contains`](https://mths.be/contains) are available, too.
46
46
47
-
## For maintainers
48
-
49
-
### How to publish a new release
50
-
51
-
1. On the `main` branch, bump the version number in `package.json`:
52
-
53
-
```sh
54
-
npm version patch
55
-
```
56
-
57
-
Instead of `patch`, use `minor` or `major` [as needed](https://semver.org/).
58
-
59
-
Note that this produces a Git commit + tag.
60
-
61
-
1. Push the release commit and tag:
62
-
63
-
```sh
64
-
git push && git push --tags
65
-
```
66
-
67
-
Our CI then automatically publishes the new release to npm.
68
-
69
47
## Author
70
48
71
49
|[](https://twitter.com/mathias"Follow @mathias on Twitter")|
0 commit comments