Plans for v3.4.22 release

[ahrtr]

The list below may change per the discussion in the community.

Issues/PRs that should be included in 3.4.22

• [3.4] etcdserver: fix memberID equals to zero in corruption alarm #14530
• [3.4] handle auth invalid token and old revision errors in watch #14548
• [3.4] avoid closing a watch with ID 0 incorrectly #14562
• [3.4] server: refresh auth info when etcd recovers from a snapshot #14649

If we backport #14589 to 3.4 (@biosvs), then we also need to backport e2e test in #14574 to 3.4 (@veshij) as well.

Please feel free to suggest any issues/PRs which should be fixed/backported in 3.4.22. cc @mitake @ptabor @serathius @spzala

[ahrtr]

release-3.4 has huge difference with main and release-3.5, it might not be easy/feasible to backport #14589 to 3.4.

The fix for #14571 is simple, and @mitake already added unit test for 3.4. I also manually verified that it's working well right now. So I will not backport or add e2e test for release-3.4. Please let me know if anyone has any concern.

[mitake]

Thanks @ahrtr , I also checked the reproducibility of the issue on my local env and confirmed release-3.4 works fine.

[ahrtr]

3.4.22 is released, thanks everyone who contributed to the release!

https://github.com/etcd-io/etcd/releases/tag/v3.4.22