Release jetstream-extra v0.3.0

[Jarema]

Signed-off-by: Tomasz Pietrek tomasz@synadia.com

[synadia-claude-reviewer]

Claude finished @Jarema's task in 1m 0s —— View job

---

PR Review

• Gather context (PR diff, CLAUDE.md, workspace Cargo files)
• Review version bump for correctness and consistency
• Post review summary

---

Summary

The change itself (bumping jetstream-extra from 0.2.1 → 0.3.0) is straightforward and correct. One issue to flag:

nats-counters/Cargo.toml still pins jetstream-extra = "0.2.1"

nats-counters declares:

jetstream-extra = { version = "0.2.1", path = "../jetstream-extra" }

In workspace builds the path takes precedence, so this compiles fine locally. But Cargo's ^0.2.1 constraint (>=0.2.1, <0.3.0) will be what ends up in the published crate on crates.io — meaning a published nats-counters would never resolve to jetstream-extra 0.3.0. If nats-counters is intended to depend on features added in 0.3.0, this needs to be bumped too.

If nats-counters is not being published alongside this release and its API doesn't rely on anything new in 0.3.0, this can be deferred — but it's worth a conscious check before the next nats-counters release.

[caspervonb]

lgtm

[piotrpio]

LGTM