Compare commits
12 Commits
ripple-bin
...
2.1.0
| Author | SHA1 | Date | |
|---|---|---|---|
|
9c4f2f4924 | ||
|
|
b18af1b8c4 | ||
|
|
1320fb03fa | ||
|
|
e5cac8aa35 | ||
|
|
1d38ec497b | ||
|
|
693110532b | ||
|
|
a1c5c82645 | ||
|
|
887cb97c2b | ||
|
|
0de4a9625f | ||
|
|
1c90c962e9 | ||
|
|
5da0db89f4 | ||
|
|
f522d3f418 |
@@ -128,16 +128,25 @@ npm uninstall abbrev -w xrpl
|
||||
1. Ensure that all tests passed on the last CI that ran on `develop`.
|
||||
2. Open a PR to update the docs if docs were modified.
|
||||
3. Create a branch off `develop` that ensures that `HISTORY.md` is updated appropriately for each package.
|
||||
* Use `shasum -a 256 build/*` to get the SHA-256 checksums. Add these to `HISTORY.md` as well.
|
||||
4. Merge this branch into `develop`.
|
||||
5. If this is not a beta release: Merge `develop` into `master` (`--ff-only`) and push to github. This is important because we have docs telling developers to use master to get the latest release.
|
||||
6. Create a new Github release/tag off of this branch.
|
||||
7. Run `npm publish --dry-run` and make sure everything looks good.
|
||||
8. Publish the release to `npm`.
|
||||
* If this is a beta release, run `npm publish --tag beta`. This allows someone else to install this version of the package with `npm install xrpl@beta`.
|
||||
* If this is a stable release, run `npm publish`.
|
||||
* This will require entering `npm` login info.
|
||||
9. Send an email to [xrpl-announce](https://groups.google.com/g/xrpl-announce).
|
||||
___
|
||||
NOW WE ARE READY TO PUBLISH! No new code changes happen manually now.
|
||||
___
|
||||
6. Checkout `master` and `git pull`.
|
||||
7. Run `npm run build` to triple check the build still works
|
||||
8. Run `npx lerna publish`. This command will diff all packages. Any changed
|
||||
package will be staged for publication.
|
||||
9. For each changed package, pick what the new version should be. Lerna will bump the versions, commit version bumps to `master`, and create a new git tag for each published package.
|
||||
10. Enter your [npmjs.com](https://npmjs.com) OTP (one-time password) to complete publication.
|
||||
___
|
||||
NOW YOU HAVE PUBLISHED! But you're not done; we have to notify people!
|
||||
___
|
||||
11. On github, click the "releases" link on the right-hand side of the page.
|
||||
12. In the top-left corner, click the "tags" toggle.
|
||||
13. For each new tag created by lerna, click the context button (the one that looks like "...") and select "new release" to create a new release from this tag.
|
||||
14. Edit the name of the release to match the tag (IE \<package\>@\<version\>) and edit the description as you see fit.
|
||||
15. Send an email to [xrpl-announce](https://groups.google.com/g/xrpl-announce).
|
||||
|
||||
## Mailing Lists
|
||||
We have a low-traffic mailing list for announcements of new `xrpl.js` releases. (About 1 email every couple of weeks)
|
||||
|
||||
|
Before Width: | Height: | Size: 9.4 KiB After Width: | Height: | Size: 9.4 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 480 B After Width: | Height: | Size: 480 B |
|
Before Width: | Height: | Size: 855 B After Width: | Height: | Size: 855 B |