update changelog to mention rustfmt and release log to remove unneces…

…sary test step
paritytech · Jun 15, 2021 · d267133 · d267133
1 parent c85da2f
commit d267133
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 11 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -9,6 +9,7 @@ The format is based on [Keep a Changelog].
 - [changed] Expose the `Origin` headers from the client handshake on `ClientRequest` [#35](https://github.com/paritytech/soketto/pull/35)
 - [changed] Update handshake error to expose a couple of new variants (`IncompleteHttpRequest` and `SecWebSocketKeyInvalidLength`) [#35](https://github.com/paritytech/soketto/pull/35)
 - [added] Add `send_text_owned` method to `Sender` as an optimisation when you can pass an owned `String` in [#36](https://github.com/paritytech/soketto/pull/36)
+- [updated] Run rustfmt over the repository, and minor tidy up [#41](https://github.com/paritytech/soketto/pull/41)
 
 ## 0.5.0
 

diff --git a/RELEASING.md b/RELEASING.md
@@ -9,23 +9,14 @@ These steps assume that you've checked out the Soketto repository and are in the
    based on the changes to date. If unsure what to bump the version to (eg is it a major, minor or patch 
    release), check with the Parity Tools team.
 
-2. Make sure that the tests pass.
-
-   ```
-   cargo test
-   ```
-
-   If anything fails, it's likely worth fixing the failures in a PR and postponing the release. Minor 
-   issues can be fixed on this release branch.
-
 3. Check that you're happy with the current documentation.
 
    ```
    cargo doc --open
    ```
 
-   It's probably a good idea to check for broken links in the documentation, which
-   can be done using the third party tool `cargo-deadlinks`:
+   CI checks for broken internal links at the moment. Optionally you can also confirm that any external links
+   are still valid like so:
 
    ```
    cargo install cargo-deadlinks