Skip to content

release: v0.12.0 — migrate to famedly-zitadel-rust-client v0.12 #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nikzen wants to merge 4 commits into
base: main
Choose a base branch
from
Open

release: v0.12.0 — migrate to famedly-zitadel-rust-client v0.12 #164

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5b66729
chore(deps): migrate to famedly-zitadel-rust-client v0.12
nikzen Jun 20, 2026
446d3b3
release: v0.12.0
nikzen Jun 20, 2026
39d097d
style: Apply nightly rustfmt
nikzen Jun 20, 2026
21fc327
refactor: Satisfy clippy too_many_lines and items_after_statements
nikzen Jun 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,20 @@

All notable changes to this project will be documented in this file.

## [0.12.0] - 2026-06-20

### Bug Fixes

- *(zitadel)* Match Zitadel error codes across the full v2 error chain, restoring the "user already exists" update path and the invalid-phone fallback

### Refactor

- *(tests)* Migrate the e2e suite from the gRPC v1 client to the v2 HTTP API

### Miscellaneous Tasks

- *(deps)* Migrate to famedly-zitadel-rust-client v0.12 and drop the v1 feature, resolving the remaining security advisories

@sirewix sirewix Jun 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was only used in tests, so probably there was no real security issues


## [0.11.2] - 2026-06-02

### Bug Fixes
Expand Down
Loading
Loading