Skip to content

Commit ae031e1

Browse files
authored
Merge pull request #56 from svix/jplatte/release
Release omniqueue v0.2.0
2 parents e6a477a + 01ba15c commit ae031e1

File tree

3 files changed

+33
-4
lines changed

3 files changed

+33
-4
lines changed

CHANGELOG.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# 0.2.0
2+
3+
This release is a big one, and we are considering omniqueue out of early development now.
4+
You can expect the API to change much less in the coming releases compared to this one.
5+
6+
## Breaking changes
7+
8+
- **redis: Some implementation changes mean that this backend is runtime-incompatible with the same backend in omniqueue 0.1**
9+
- Revise the public module structure to shorten import paths and make the docs easier to navigate
10+
- Revise the public API to require fewer trait imports for common usage
11+
- Rename a few types and traits
12+
- Most notably, `MemoryQueueBackend` is now named `InMemoryBackend`
13+
- Everything else should be easily found by searching for the old names
14+
- Remove custom encoders / decoders
15+
- Custom encoding can be handled more efficiently by wrapping omniqueue's
16+
`raw` send / receive interfaces into a custom higher-level interface
17+
- Update and prune dependency tree
18+
- Switch omniqueue's public traits from `async_trait` to [native async-in-traits][]
19+
- Simplify generic bounds (only matters if you were using omniqueue in generic code)
20+
21+
## Additions
22+
23+
- Add a backend for Google Cloud's Pub/Sub queue (`gcp_pubsub` feature / module)
24+
- Add some documentation
25+
- Introduce an `omniqueue::Result` type alias
26+
27+
[native async-in-traits]: https://blog.rust-lang.org/2023/12/21/async-fn-rpit-in-traits.html
28+
29+
# 0.1.0
30+
31+
Initial release.

README.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ types for which you have provided an encoding and/or decoding function.
1616
It is designed to be flexible and to be able to adapt to fit your existing queue configurations, but
1717
with a set of defaults that makes it simple to start sending and receiving quickly.
1818

19-
Omniqueue is still early in development.
20-
2119
## How to use Omniqueue
2220

2321
While the exact configuration will depend on the backend used, usage is roughly as follows.

omniqueue/Cargo.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "omniqueue"
3-
version = "0.1.0"
3+
version = "0.2.0"
44
license = "MIT"
55
description = "An abstraction layer over various queue backends"
66
authors = ["Svix Inc. <oss@svix.com>"]
@@ -17,7 +17,7 @@ bb8 = { version = "0.8", optional = true }
1717
bb8-redis = { version = "0.14.0", optional = true }
1818
futures-util = { version = "0.3.28", default-features = false, features = ["async-await", "std"], optional = true }
1919
google-cloud-googleapis = { version = "0.12.0", optional = true }
20-
google-cloud-pubsub = { version = "0.22.1", optional = true }
20+
google-cloud-pubsub = { version = "0.23.0", optional = true }
2121
lapin = { version = "2", optional = true }
2222
redis = { version = "0.24.0", features = ["tokio-comp", "tokio-native-tls-comp", "streams"], optional = true }
2323
serde = "1.0.196"

0 commit comments

Comments
 (0)