|
1 | 1 | Contributing |
2 | 2 | ============ |
3 | 3 |
|
| 4 | +The release process for Bitvavo SDK for Node.js is semi-automatic. You manually start the GitHub Action that creates |
| 5 | +the SDK package and uploads it to [npmjs](https://www.npmjs.com/package/bitvavo). |
| 6 | + |
4 | 7 | ## Prerequisites |
5 | | -To release the SDK from your local development device you need: |
6 | | -- Node installed on your development device |
| 8 | + |
| 9 | +To release the SDK you need to: |
| 10 | + |
| 11 | +- Complete the instructions in the [README Prerequisites](./README.md#prerequisites) |
7 | 12 | - Clone https://github.com/bitvavo/node-bitvavo-api to your development device |
8 | | -- The [Bitvavo password for NPM] from the Exchange Backbone team vault in 1Password |
9 | 13 |
|
10 | | -## Test and Publish the SDK |
11 | | -After you have made your changes to the SDK, to publish Bitvavo SDK for Node.js: |
12 | | -1. **Test the package** |
| 14 | +## Release a new version of the SDK |
| 15 | + |
| 16 | +To update the SDK and publish your changes to the Bitvavo developer community: |
| 17 | + |
| 18 | +1. **Make your updates to the SDK** |
| 19 | + |
| 20 | + Create a branch and implement your changes to the SDK. |
| 21 | + |
| 22 | +2. **Test the package** |
13 | 23 | 1. Run the smoke tests in `<repo-root>/example/testApi.js` |
14 | | -2. **Release the SDK** |
15 | | - 1. Run the [Release workflow]. Use [Semver] to choose the version number. |
16 | | - 2. Fill out the notes in the [drafted release](https://github.com/bitvavo/node-bitvavo-api/releases). |
17 | | - 3. Publish the release. |
| 24 | + 1. When your code passes the smoke tests, make a pull request |
| 25 | + to the `master` branch. |
| 26 | + |
| 27 | +1. **Publish the SDK** |
| 28 | + |
| 29 | + 1. When your [pull request](https://github.com/bitvavo/node-bitvavo-api/pulls) is approved, merge your changes to |
| 30 | + the `master` branch. |
| 31 | + 1. Note the release number of the |
| 32 | + [latest version of the SDK published to npmjs](https://www.npmjs.com/package/bitvavo?activeTab=versions) |
| 33 | + and using [semver](https://semver.org/) as your guide, decide on a version number for this release. |
| 34 | + 1. In Actions, [run the release action](https://github.com/bitvavo/node-bitvavo-api/actions/workflows/release.yml) |
| 35 | + using your new release number. |
| 36 | + |
| 37 | + 1. Open the draft release created when you ran the release action. |
| 38 | + 1. Add a brief description about the release. |
| 39 | + |
| 40 | + This description is visible to the world in https://github.com/bitvavo/node-bitvavo-api/releases. |
| 41 | + 1. Click **Publish**. |
| 42 | + |
| 43 | + This starts the Publish action. You see the |
| 44 | + [new version available on npmjs](https://www.npmjs.com/package/bitvavo). |
| 45 | + |
| 46 | +Now send the release message in Slack, yay. |
18 | 47 |
|
19 | | -The new version is published to https://www.npmjs.com/package/bitvavo. |
20 | 48 |
|
21 | | -[Bitvavo password for NPM]: https://start.1password.com/open/i?a=YUSMSDGGJBG5JDUAGUSBP4GYWM&v=asrum7nvbb2agfh3ob532ekbfy&i=f3i334rmzgxejycgufdwiiua3u&h=bitvavo.1password.com |
22 | | -[Release workflow]: https://github.com/bitvavo/node-bitvavo-api/actions/workflows/release.yml |
23 | | -[Semver]: https://semver.org/ |
|
0 commit comments