Not only that, there are more items not fully in sync with upstream.
Now i do not know if this is something fully new since 2026.3.0 or a bit earlier too.
We need to check and validate the response again.
<!-- gh-comment-id:4106082993 -->
@BlackDex commented on GitHub (Mar 22, 2026):
Not only that, there are more items not fully in sync with upstream.
Now i do not know if this is something fully new since 2026.3.0 or a bit earlier too.
We need to check and validate the response again.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @flipper on GitHub (Mar 22, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6988
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.35.4
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
traefik
Host/Server Operating System
Linux
Operating System Version
No response
Clients
CLI
Client Version
No response
Steps To Reproduce
Expected Result
Expected response is that Vaultwarden returns the same API response as the official server.
Actual Result
Vaultwarden responds with the deserialized version of the data object
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Mar 22, 2026):
Not only that, there are more items not fully in sync with upstream.
Now i do not know if this is something fully new since 2026.3.0 or a bit earlier too.
We need to check and validate the response again.