From 9e8ced2b8ab7268d4aa7b293d5457c95ddb420a4 Mon Sep 17 00:00:00 2001
From: David Pedersen <david.pdrsn@gmail.com>
Date: Mon, 25 Apr 2022 15:29:12 +0200
Subject: [PATCH] Release 0.3.0

---
 tower-http/CHANGELOG.md | 47 +++++++++++++++++++++++++++++------------
 tower-http/Cargo.toml   |  2 +-
 2 files changed, 34 insertions(+), 15 deletions(-)

diff --git a/tower-http/CHANGELOG.md b/tower-http/CHANGELOG.md
index a0880ed3..c2630075 100644
--- a/tower-http/CHANGELOG.md
+++ b/tower-http/CHANGELOG.md
@@ -9,38 +9,57 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## Added
 
-- Add `ServeDir::{fallback, not_found_service}` for calling another service if
-  the file cannot be found.
-- Add `SetStatus` to override status codes.
+- None.
+
+## Changed
+
+- None.
+
+## Removed
+
+- None.
+
+## Fixed
+
+- None.
+
+# 0.3.0 (April 25, 2022)
+
+## Added
+
+- **fs**: Add `ServeDir::{fallback, not_found_service}` for calling another service if
+  the file cannot be found ([#243])
+- **fs**: Add `SetStatus` to override status codes ([#248])
 - `ServeDir` and `ServeFile` now respond with `405 Method Not Allowed` to requests where the
-  method isn't `GET` or `HEAD`.
+  method isn't `GET` or `HEAD` ([#249])
 - **cors**: Added `CorsLayer::very_permissive` which is like
   `CorsLayer::permissive` except it (truly) allows credentials. This is made
   possible by mirroring the request's origin as well as method and headers
-  back as CORS-whitelisted ones
-- **cors**: Allow customizing the value(s) for the `Vary` header
+  back as CORS-whitelisted ones ([#237])
+- **cors**: Allow customizing the value(s) for the `Vary` header ([#237])
 
 ## Changed
 
 - **cors**: Removed `allow-credentials: true` from `CorsLayer::permissive`.
   It never actually took effect in compliant browsers because it is mutually
-  exclusive with the `*` wildcard (`Any`) on origins, methods and headers
+  exclusive with the `*` wildcard (`Any`) on origins, methods and headers ([#237])
 - **cors**: Rewrote the CORS middleware. Almost all existing usage patterns
-  will continue to work. (BREAKING)
+  will continue to work. (BREAKING) ([#237])
 - **cors**: The CORS middleware will now panic if you try to use `Any` in
   combination with `.allow_credentials(true)`. This configuration worked
   before, but resulted in browsers ignoring the `allow-credentials` header,
-  which defeats the purpose of setting it and can be very annoying to debug.
-
-## Removed
-
-- None.
+  which defeats the purpose of setting it and can be very annoying to debug
+  ([#237])
 
 ## Fixed
 
-- Fix content-length calculation on range requests ([#228])
+- **fs**: Fix content-length calculation on range requests ([#228])
 
 [#228]: https://github.com/tower-rs/tower-http/pull/228
+[#237]: https://github.com/tower-rs/tower-http/pull/237
+[#243]: https://github.com/tower-rs/tower-http/pull/243
+[#248]: https://github.com/tower-rs/tower-http/pull/248
+[#249]: https://github.com/tower-rs/tower-http/pull/249
 
 # 0.2.4 (March 5, 2022)
 
diff --git a/tower-http/Cargo.toml b/tower-http/Cargo.toml
index e31ed622..84ed6217 100644
--- a/tower-http/Cargo.toml
+++ b/tower-http/Cargo.toml
@@ -1,7 +1,7 @@
 [package]
 name = "tower-http"
 description = "Tower middleware and utilities for HTTP clients and servers"
-version = "0.2.3"
+version = "0.3.0"
 authors = ["Tower Maintainers <team@tower-rs.com>"]
 edition = "2018"
 license = "MIT"