Livio Spring 57e8033b6e fix: use hash to compare user metadata value (#10749) ...

# Which Problems Are Solved

Depending on the metadata values (already existing), the newly created
index (#10415) cannot be created or error in the future.

# How the Problems Are Solved

- Create the index using `sha256` and change the query to use sha256 as
well when comparing bytes values such as user_metadata.
- Added a setup step to cleanup potentially created index on
`projections.user_metadata5`

# Additional Changes

None

# Additional Context

- relates to #10415 
- requires backport to v4.x

2025-09-18 09:50:56 +00:00

..

admin

chore: test server for direct resource access

2023-04-24 20:40:31 +03:00

build

fix(cache): use key versioning (#10657)

2025-09-15 09:51:54 +00:00

encryption

feat: action v2 signing (#8779)

2024-11-28 10:06:52 +00:00

hooks

feat: support whole config as env (#6336)

2024-02-16 16:04:42 +00:00

initialise

chore!: Introduce ZITADEL v3 (#9645)

2025-04-02 16:53:06 +02:00

key

chore!: Introduce ZITADEL v3 (#9645)

2025-04-02 16:53:06 +02:00

mirror

feat: http provider signing key addition (#10641)

2025-09-08 11:00:04 +00:00

ready

feat(v3alpha): web key resource (#8262)

2024-08-14 14:18:14 +00:00

setup

fix: use hash to compare user metadata value (#10749)

2025-09-18 09:50:56 +00:00

start

fix: use a single translator for middleware (#10633)

2025-09-09 06:34:59 +00:00

tls

fix: enable env vars in setup steps (and deprecate admin subcommand) (#3871)

2022-06-27 10:32:34 +00:00

defaults.yaml

fix(service ping): log body size of reports (#10686)

2025-09-16 07:04:17 +00:00

zitadel.go

fix(mirror): read config correctly (#8330)

2024-07-18 14:00:58 +00:00