* chore(release): v0.14.0

* Update CHANGELOG.md

* Update CHANGELOG.md

* initial rewrite to re-use HTTP access control

* clean things up

* Update core/src/error.rs

* Update core/src/error.rs

* allow origin: add back removed Display impl

* cleanup again

* Update http-server/src/lib.rs

* Update examples/examples/cors_server.rs

* Update core/src/server/access_control/mod.rs

Co-authored-by: Tarik Gul <[email protected]>

* Update http-server/src/server.rs

Co-authored-by: Tarik Gul <[email protected]>

* fix bad comment

* remove todo

* fix grumbles

* more grumbles

* rename and document a bit

* remove `Access-Control-Allow-Origin` in whitelist

* fix nit: pub(super)

* fix bad naming

Co-authored-by: Tarik Gul <[email protected]>

* fix(http server): omit jsonrpc details health API

Closing https://github.com/paritytech/jsonrpsee/issues/784
Ordinary GET requests doesn't expect the body the be formatted as
`JSON-RPC` responses which this fixes.

* address grumbles

* Update http-server/src/server.rs

* cargo fmt

* chore(release): v0.13.1

* Update CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: Tarik Gul <[email protected]>

* Update CHANGELOG.md

Co-authored-by: Tarik Gul <[email protected]>

* chore(release): v0.13.0

* Update CHANGELOG.md

* feat: limit the number of subscriptions

Closing #729

* fix nit

* Update core/src/server/helpers.rs

* add integration tests + some fixes so it works

* cargo fmt

* fix doc links

* Unsubscribe calls should avoid subscription limits

Point to Tokio 1.16 (we use a method from it), and a little special treatment for unsubscribe methods

* No resource limiting for Unsubscribe calls

* Test that we can still unsubscribe after hitting a limit

* Fix a comment typo

Co-authored-by: Alexandru Vasile <[email protected]>

* Update core/src/server/rpc_module.rs

* Update core/src/server/rpc_module.rs

Co-authored-by: James Wilson <[email protected]>
Co-authored-by: Alexandru Vasile <[email protected]>

* chore(release): v0.11.0

* remove unused deps

* docs: rephrase bad english

* Update CHANGELOG.md

* update publish script

* Update CHANGELOG.md

Co-authored-by: David <[email protected]>

* Update CHANGELOG.md

Co-authored-by: David <[email protected]>

* Update CHANGELOG.md

Co-authored-by: David <[email protected]>

Co-authored-by: David <[email protected]>

* refactor(log): downgrade send errors to warn

These logs are most likely related to that the client terminated the connection
and they come with significant overhead.

* chore(release): v0.10.1

* update changelog

* update versions v0.10.0

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: Tarik Gul <[email protected]>

* Update CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: Tarik Gul <[email protected]>

* unify servers; use tokio::TcpListener

* add API to build server from tcp socket

* build_from_tcp nit: not async

* fix nits

* change `build_from_tcp` force users configure hyper

The hyper settings might contradict to settings on the provided
socket, force users of this API to configure that avoid confusion and
unexpected settings.

* Update http-server/src/server.rs

* fix doc links

* add separate APIs `build_from_tcp` and `build_from_hyper`

* fix clippy

* remove dead code

* fix build

* fix nit in example code

* Release prep for v0.9

* Update CHANGELOG
Don't dry-run when releasing

* Tweak release notes

* Update CHANGELOG.md

Co-authored-by: Niklas Adolfsson <[email protected]>

Co-authored-by: Niklas Adolfsson <[email protected]>

* Prep for releasing v0.8.0

* Grumble

* chore: release v0.7.0

* Update CHANGELOG.md

* Update CHANGELOG.md

* update changelog

* Tweak CHANGELOG

* re-export core for clients as well

Co-authored-by: David Palm <[email protected]>

Implies MSRV 1.56.x

* extract ws client to async client

* bring back jsonrpsee-ws-client crate

* new crate core client

* add missing file

* jsonrpsee crate: add core client

* rexport core client

* more re-exports

* downgrade trait bounds

* update version

* fix nits

* send close reason

* Update types/src/traits.rs

* move 'TEN_MB_CONST' to core

* Update client/core-client/Cargo.toml

Co-authored-by: David <[email protected]>

* Update client/core-client/src/lib.rs

Co-authored-by: David <[email protected]>

* cargo fmt

* Update client/ws-client/src/lib.rs

Co-authored-by: David <[email protected]>

* Update client/ws-client/src/lib.rs

Co-authored-by: David <[email protected]>

* move `async-client` core

The `async-client` is hidden behind a new feature flag `async-client`
because it brings in additional dependecies such as tokio rt.

* fix docs

* add example how to use "core client"

* fix build

* Update http-server/Cargo.toml

* Update client/transport/Cargo.toml

Co-authored-by: David <[email protected]>

* Nuke V2

* fmt

* Formatting and imports

* Updated benches

* Fix doc comment link

* Brace imports in ws-server

* Reworking imports

* std first

* fmt

* std on top

* Update to match changed line numbers

* Rename jsonrpsee_utils -> jsonrpsee_core

* Migrating things types -> core

* RpcError -> ErrorResponse

* Merge types::client into core::client

* Continued move types -> core

* Removing features to make checks pass

* Move rpc_module tests to tests crate

* Fixed doc comment links

* Add futures-util dependency for client

* Remove dead code

Co-authored-by: Niklas Adolfsson <[email protected]>

* fmt

* Feature gate the Client trait

* Move `Client` traits to `client` module

Co-authored-by: Niklas Adolfsson <[email protected]>

* Bump version –> 0.5
Fix try-build tests

* Changelog

* Update CHANGELOG.md

Co-authored-by: Niklas Adolfsson <[email protected]>

* Update CHANGELOG.md

Co-authored-by: Niklas Adolfsson <[email protected]>

* update CHANGELOG

* bump version number

* fix nit

* Update CHANGELOG.md

Co-authored-by: David <[email protected]>

* bullet list in CHANGELOG

* add last item to CHANGELOG

Co-authored-by: David <[email protected]>

* Document resource limiting

* Formatting

* More formatting

* fmt

* Doc comment wording

Co-authored-by: David <[email protected]>

* Cross-reference docs between servers and utils

* Fix grumbles

* More elaborate description

* Update http-server/Cargo.toml

Co-authored-by: Niklas Adolfsson <[email protected]>

* Apply suggestions from code review

Co-authored-by: David <[email protected]>

* Allow for unlimited resources if cap is 0

* fmt

* Update ws-server/Cargo.toml

Co-authored-by: Niklas Adolfsson <[email protected]>

* Clarify 8 resources, 0s in costs/limits, and runtime errors

Co-authored-by: David <[email protected]>
Co-authored-by: Niklas Adolfsson <[email protected]>

Co-authored-by: David Palm <[email protected]>

To make sure that we are not affected by:
	- https://github.com/hyperium/hyper/security/advisories/GHSA-f3pg-qwvg-p99c
	- https://github.com/hyperium/hyper/security/advisories/GHSA-5h46-h7hh-c6x9

However, `hyper 13` is not fixed but I think we should remove that support anyway?!

Updates the requirements on [env_logger](https://github.com/env-logger-rs/env_logger) to permit the latest version.
- [Release notes](https://github.com/env-logger-rs/env_logger/releases)
- [Changelog](https://github.com/env-logger-rs/env_logger/blob/main/CHANGELOG.md)
- [Commits](https://github.com/env-logger-rs/env_logger/compare/v0.8.0...v0.9.0

)

---
updated-dependencies:
- dependency-name: env_logger
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump versions to 0.3.0

* Add draft release checklist

* Changelog for v0.3.0

* Mention possibility of passing params to `publish.sh`

* Added PR 412

* Release prep

* Mention proc macro limitations

* Mention publish script

This PR requires the internal dependencies to require the exact version
because `cargo` will otherwise fetch the latest version.

This could also be achievied by `cargo update -p package --precise x.y.z`.

Should be reverted once we release 0.2

The reason is that `Receiver::next` won't panic polling after `Ok(None)` has been received.

* Switch from anyhow::Result to std Result

* fmt

* Use thiserror `#[from]`

* Remove sadness

* prep to release 0.2.0-alpha.5

* fix features

* update readme

* add changelog

* add metadata to the crates on crates.io