From f1ea234dd7b1227796f507225fc3015103dd82bb Mon Sep 17 00:00:00 2001 From: Paul Bellamy Date: Tue, 11 May 2021 19:32:04 +0100 Subject: [PATCH] Fix broken links to js-stellar-base repo --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8641ca381..140f816d8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,9 +6,9 @@ Then please [sign the Contributor License Agreement](https://docs.google.com/for # Releasing -Just like with the [js-stellar-base](https://github.com/stellar/js-stellar) library, there are a few important things to remember when releasing a new version of the library. +Just like with the [js-stellar-base](https://github.com/stellar/js-stellar-base) library, there are a few important things to remember when releasing a new version of the library. -In fact, you should follow [the steps there](https://github.com/stellar/js-stellar/base/blob/master/CONTRIBUTING.md#Releasing), first, except for this repository. Then, **if base has been updated**, you want to follow the additional steps here: +In fact, you should follow [the steps there](https://github.com/stellar/js-stellar-base/blob/master/CONTRIBUTING.md#Releasing), first, except for this repository. Then, **if base has been updated**, you want to follow the additional steps here: - [ ] First, bump its version accordingly. This is straightforward: change the version field of `"stellar-base"` under the `"dependencies"` section in the SDK's [package.json](https://github.com/stellar/js-stellar-sdk/blob/master/package.json#L140), e.g.: