Skip to content

Commit

Permalink
Merge pull request #92 from fastly/release-0.2.6
Browse files Browse the repository at this point in the history
📦 Release Viceroy 0.2.6
  • Loading branch information
katelyn martin authored Nov 17, 2021
2 parents b85d0f5 + dba7cbd commit 2228240
Show file tree
Hide file tree
Showing 6 changed files with 14 additions and 8 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
## Unreleased

## 0.2.6 (2021-11-15)

- Catch interrupt signals ([#85](https://github.com/fastly/Viceroy/pull/85))
- Include aarch64 tarballs for Linux and macOS ([#88](https://github.com/fastly/Viceroy/pull/88))
- Align URI and Host header semantics with production C@E ([#90](https://github.com/fastly/Viceroy/pull/90))

## 0.2.5 (2021-10-21)

- Replaced `hyper-tls` with `hyper-rustls`. ([#75](https://github.com/fastly/Viceroy/pull/75))
Expand Down
4 changes: 2 additions & 2 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion cli/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[package]
name = "viceroy"
description = "Viceroy is a local testing daemon for Compute@Edge."
version = "0.2.6"
version = "0.2.7"
authors = ["Fastly"]
edition = "2018"
license = "Apache-2.0 WITH LLVM-exception"
Expand Down
2 changes: 1 addition & 1 deletion cli/tests/trap-test/Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 3 additions & 3 deletions doc/RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Below are the steps needed to do a Viceroy release:
crates.io registry. Note that we must do this in order of dependencies. So,
1. `cd lib && cargo publish`
1. `cd cli && cargo publish`
1. Now, we should return to our release PR and push a commit to the branch that
bumps Viceroy to the next patch version (so `z + 1`) and updates all the
lockfiles again.
1. Now, we should return to our release PR and add a commit to the branch that
bumps Viceroy to the next patch version (so `z + 1`). Then, update all the
lockfiles by running `make fix-build`.
1. Get another approval and merge when CI passes.
2 changes: 1 addition & 1 deletion lib/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "viceroy-lib"
version = "0.2.6"
version = "0.2.7"
description = "Viceroy implementation details."
authors = ["Fastly"]
edition = "2018"
Expand Down

0 comments on commit 2228240

Please sign in to comment.