Not me, I think, I haven't been running a Vaultwarden server since I left Autonomic (back to the warm embrace of Zx2c4 password-store for me). Good luck, happy hacking 👋
Not me, I think, I haven't been running a Vaultwarden server since I left Autonomic (back to the warm embrace of Zx2c4 password-store for me). Good luck, happy hacking 👋
remaining parts are:
- creating the vw-maintainers team (asked in matrix because I don't have such powers 😆)
- [repo persmissions](https://docs.coopcloud.tech/maintainers/maintain/#repository-permissions) (depends on previous step)
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.
See: https://docs.coopcloud.tech/maintainers/maintain/
CC (most recent contributors): @joe-irving @fauno @3wordchant @moritz @knoflook
thanks. i could co-maintain since we use vw a lot
Not me, I think, I haven't been running a Vaultwarden server since I left Autonomic (back to the warm embrace of Zx2c4 password-store for me). Good luck, happy hacking 👋
meanwhile i asked @3wordchant to ask comrade renovate to monitor this repo #16
i went ahead and published the 1.35 upgrade with a patch recipe version since it deploys without issues.
Okay, I'm happy to co-maintain with you @fauno
I'll work on the maintainer PR rn
created #20
remaining parts are:
Added you as owner of both orgs (
toolshed/coop-cloud) @ammaratef45 ✅tysm @decentral1se
@fauno we are ready to go once you approve and merge #20 ! 👯