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
PRs should be made against and merged into the [`dev-5.x`](https://github.com/hossein-zare/react-native-dropdown-picker) branch, which is set as the `default` branch on github.
25
+
PRs should be made against and merged into
26
+
the [`dev-5.x`](https://github.com/hossein-zare/react-native-dropdown-picker)
27
+
branch, which is set as the `default` branch on GitHub.
21
28
22
-
### Release
29
+
####Release
23
30
24
-
Releases are currently made from the [`5.x`](https://github.com/hossein-zare/react-native-dropdown-picker/tree/5.x) branch.
31
+
Releases are currently made from
32
+
the [`5.x`](https://github.com/hossein-zare/react-native-dropdown-picker/tree/5.x)
33
+
branch.
25
34
26
-
## Release Process
35
+
###Release Process
27
36
28
37
To make a new release, follow these steps:
29
38
30
-
* Verify the development branch has all the changes desired in a release and works well
31
-
* Make and merge a final PR into development branch that increments the version number in `package.json`
39
+
* Verify the development branch has all the changes desired in the release and
40
+
works well
41
+
* Use `npm pack` to test the new version of the library locally and check it
42
+
works correctly;
43
+
see [https://dev.to/scooperdev/use-npm-pack-to-test-your-packages-locally-486e](https://dev.to/scooperdev/use-npm-pack-to-test-your-packages-locally-486e)
44
+
* Make and merge a final PR into the development branch that increments the
45
+
version number in `package.json`
32
46
* Make and merge a PR from the development branch to the release branch
33
-
* Using the GitHub web UI, draft a new release using tag name `vx.x.x` (replace the `x` values as appropriate of course), with the release branch as the target, with release name `vx.x.x` (again, with appropriate numbers in place of `x` of course)
34
-
* Verify in the GitHub Actions panel for the repository that NPM publish succeeded
47
+
* Using the GitHub web UI, draft a new release using the tag name `vx.x.x`
48
+
(replace the `x` values as appropriate). Use the release branch as the
49
+
target, with the release name being `vx.x.x` (again, with appropriate
50
+
numbers in place of `x`)
51
+
* Verify in the GitHub Actions panel for the repository that `npm publish`
52
+
succeeded
53
+
54
+
[//]: # (TODO: make templates for pull requests and issues, and CONTRIBUTING.md
55
+
include check people read docs and past issues before submitting new issues
56
+
ensure PRs tested with npm pack: https://dev.to/scooperdev/use-npm-pack-to-test-your-packages-locally-486e
0 commit comments